스킬 tdd-guide

🧪

tdd-guide

Name: tdd-guide
Author: alirezarezvani

안전 📁 파일 시스템 액세스🔑 환경 변수🌐 네트워크 접근⚙️ 외부 명령어

Guide Test-Driven Development with AI-Powered Workflows

Writing tests after code leads to incomplete coverage and technical debt. This skill enforces TDD discipline by guiding you through red-green-refactor cycles with intelligent test generation and coverage analysis.

지원: Claude Codex Code(CC)

📊 69 적절함

스킬 ZIP 다운로드

Claude에서 업로드

설정 → 기능 → 스킬 → 스킬 업로드로 이동

토글을 켜고 사용 시작

테스트해 보기

"tdd-guide" 사용 중입니다. Analyze test coverage for my user service module

예상 결과:

Coverage analysis: 12 functions analyzed, 8 tested, 4 untested
Missing tests: createUser(), deleteUser(), updateUserEmail(), validatePassword()
Recommended priority: HIGH for deleteUser (destructive operation), MEDIUM for others
Next step: Generate test template for deleteUser function with rollback scenarios

"tdd-guide" 사용 중입니다. Generate tests for my API endpoint handler

예상 결과:

Test framework detected: Jest with Supertest
Generated 6 test cases: success response, authentication failure, validation errors, rate limiting, timeout handling, database connection loss
Test structure: Arrange-Act-Assert pattern with setup and teardown hooks
Estimated coverage improvement: 45% to 89% for this endpoint

"tdd-guide" 사용 중입니다. Guide me through TDD for a shopping cart feature

예상 결과:

Step 1 RED: Write failing test for addItemToCart with quantity validation
Step 2 GREEN: Implement minimal code to pass the test - basic item addition only
Step 3 REFACTOR: Extract duplicate quantity logic into validateQuantity helper
Step 4: Repeat cycle for removeItem, updateQuantity, and clearCart operations

보안 감사

안전

v3 • 1/16/2026

This skill is a legitimate TDD workflow tool. The 309 static findings are false positives from test fixtures and documentation examples. The code analyzes test files, generates test recommendations, and formats output - all standard development tool operations with no malicious intent.

스캔된 파일

5,453

분석된 줄 수

발견 사항

총 감사 수

위험 요인

📁 파일 시스템 액세스 (13)

evaluation_output.json:48 evaluation_output.json:48 README.md:80 README.md:85 README.md:77 README.md:80 README.md:85 sample_input_typescript.json:4 sample_input_typescript.json:4 sample_input_typescript.json:4 sample_input_typescript.json:4 test_generator.py:329 test_generator.py:368

🔑 환경 변수 (2)

evaluation_output.json:60 README.md:100

🌐 네트워크 접근 (6)

fixture_generator.py:138 fixture_generator.py:139 fixture_generator.py:140 README.md:69 README.md:631 skill-report.json:6

⚙️ 외부 명령어 (110)

HOW_TO_USE.md:9-19 HOW_TO_USE.md:19-23 HOW_TO_USE.md:23-32 HOW_TO_USE.md:32-36 HOW_TO_USE.md:36-48 HOW_TO_USE.md:48-54 HOW_TO_USE.md:54-59 HOW_TO_USE.md:59-65 HOW_TO_USE.md:65-72 HOW_TO_USE.md:72-76 HOW_TO_USE.md:76-89 HOW_TO_USE.md:89-93 HOW_TO_USE.md:93-98 HOW_TO_USE.md:98-109 HOW_TO_USE.md:109-116 HOW_TO_USE.md:116-120 HOW_TO_USE.md:120-125 HOW_TO_USE.md:125-137 HOW_TO_USE.md:137-140 HOW_TO_USE.md:140-144 HOW_TO_USE.md:144-160 HOW_TO_USE.md:160-236 HOW_TO_USE.md:236-245 HOW_TO_USE.md:245-249 HOW_TO_USE.md:249-261 HOW_TO_USE.md:261-265 HOW_TO_USE.md:265-279 HOW_TO_USE.md:279-283 HOW_TO_USE.md:283-284 HOW_TO_USE.md:284-285 output_formatter.py:153 output_formatter.py:248 output_formatter.py:250 README.md:67-72 README.md:72-75 README.md:75-81 README.md:81-84 README.md:84-87 README.md:87-91 README.md:91-96 README.md:96-107 README.md:107-113 README.md:113-122 README.md:122-126 README.md:126-132 README.md:132-136 README.md:136-143 README.md:143-212 README.md:212-225 README.md:225-228 README.md:228-259 README.md:259-264 README.md:264-279 README.md:279-282 README.md:282-297 README.md:297-302 README.md:302-310 README.md:310-315 README.md:315-323 README.md:323-326 README.md:326-341 README.md:341-360 README.md:360-366 README.md:366-371 README.md:371-383 README.md:383-386 README.md:386-402 README.md:402-403 README.md:403-407 README.md:407-411 README.md:411-432 README.md:432-438 README.md:438-444 README.md:444-456 README.md:456-460 README.md:460-462 README.md:462-479 README.md:479-558 README.md:558-561 README.md:561-564 README.md:564-568 README.md:568-571 README.md:571-575 README.md:575-578 README.md:578-582 README.md:582-585 README.md:585-589 README.md:589-593 README.md:593-612 README.md:612-619 README.md:619-622 README.md:622-623 README.md:623-624 README.md:624-629 README.md:629-645 SKILL.md:91-98 SKILL.md:98-101 SKILL.md:101-107 SKILL.md:107-110 SKILL.md:110-119 SKILL.md:119-122 SKILL.md:122-127 SKILL.md:127-227 SKILL.md:227-231 SKILL.md:231-234 SKILL.md:234-238 SKILL.md:238-241 SKILL.md:241-245 SKILL.md:245-248 SKILL.md:248-252

감사자: claude 감사 이력 보기 →

품질 점수

아키텍처

100

유지보수성

콘텐츠

커뮤니티

100

보안

사양 준수

만들 수 있는 것

Learn TDD fundamentals with guided examples

Get step-by-step instructions for writing your first test cases and implementing features test-first with real-time feedback.

Retrofit tests into existing untested codebases

Identify missing test coverage across legacy projects and generate comprehensive test suites to improve reliability.

Establish TDD workflows in development teams

Set up automated TDD checks in code review processes and CI pipelines to maintain high test coverage across projects.

이 프롬프트를 사용해 보세요

Analyze test coverage

Analyze my current test coverage and show me which functions in the src directory do not have corresponding unit tests

Generate test template

Generate a comprehensive test suite for the calculateDiscount function in src/pricing.py including edge cases and error conditions

Start TDD cycle

Guide me through a TDD cycle to implement a new user authentication feature starting with test cases first

Review test quality

Review my test suite for the payment processing module and suggest improvements for better coverage and edge case handling

모범 사례

Run the coverage analysis before starting new features to establish baseline metrics
Write tests for one function at a time following the red-green-refactor cycle completely
Review generated test templates and customize them to match your specific business logic requirements

피하기

Generating all tests at once without implementing code incrementally between test cycles
Skipping the refactor step after tests pass and accumulating technical debt in test code
Relying solely on generated tests without adding domain-specific edge cases your team knows about

자주 묻는 질문

Which programming languages and testing frameworks are supported?

Python (pytest, unittest), TypeScript/JavaScript (Jest, Mocha, Vitest), Ruby (RSpec, Minitest), and Go (testing package). Framework auto-detection included.

Does this tool execute my tests or measure actual coverage?

No, it analyzes code structure and generates test templates. You must run tests using your existing test runner and coverage tools.

Can I customize the test generation templates for my team standards?

Yes, the tool provides base templates that you should review and modify to match your team conventions, naming patterns, and assertion styles.

How does the coverage analysis work without running tests?

It performs static analysis by matching source files to test files using naming conventions and import statements to identify untested code paths.

Will this work with my existing CI/CD pipeline?

Yes, output formats include JSON for automated parsing. Integrate coverage reports into pull request checks or quality gates in your pipeline.

What if my codebase uses a custom testing framework?

The tool may not detect custom frameworks automatically. You can still use it by manually specifying the framework format in your configuration.