Source profileQuality 84/100

aAAaqwq/AGI-Super-Team/skills/tdd-guide/SKILL.md

tdd-guide

Test-driven development workflow with test generation, coverage analysis, and multi-framework support

Source repository stars
82
Declared platforms
0
Static risk flags
0
Last source update
2026-08-04
Source checked
2026-08-04
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSource

Decision brief

What it does—and where it fits

Test-driven development skill for generating tests, analyzing coverage, and guiding red-green-refactor workflows across Jest, Pytest, JUnit, and Vitest.

Best for

    Not for

    • E2E testing: Playwright, Cypress, Selenium
    • Performance testing: k6, JMeter, Locust

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/aAAaqwq/AGI-Super-Team --skill "skills/tdd-guide"
    Safe inspection promptEditorial

    Inspect the Agent Skill "tdd-guide" from https://github.com/aAAaqwq/AGI-Super-Team/blob/a1b3bf19948a6f3da84347c920a23fc2799d8824/skills/tdd-guide/SKILL.md at commit a1b3bf19948a6f3da84347c920a23fc2799d8824. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      Capabilities

      Review the “Capabilities” section in the pinned source before continuing.

      Review and apply the “Capabilities” source section.
    2. 02

      Workflows

      1. Provide source code (TypeScript, JavaScript, Python, Java) 2. Specify target framework (Jest, Pytest, JUnit, Vitest) 3. Run testgenerator.py with requirements 4. Review generated test stubs 5. Validation: Tests compile and cover happy path, error cases, edge cases

      Provide source code (TypeScript, JavaScript, Python, Java)Specify target framework (Jest, Pytest, JUnit, Vitest)Run testgenerator.py with requirements
    3. 03

      Generate Tests from Code

      1. Provide source code (TypeScript, JavaScript, Python, Java) 2. Specify target framework (Jest, Pytest, JUnit, Vitest) 3. Run testgenerator.py with requirements 4. Review generated test stubs 5. Validation: Tests compile and cover happy path, error cases, edge cases

      Provide source code (TypeScript, JavaScript, Python, Java)Specify target framework (Jest, Pytest, JUnit, Vitest)Run testgenerator.py with requirements
    4. 04

      Analyze Coverage Gaps

      1. Generate coverage report from test runner (npm test -- --coverage) 2. Run coverageanalyzer.py on LCOV/JSON/XML report 3. Review prioritized gaps (P0/P1/P2) 4. Generate missing tests for uncovered paths 5. Validation: Coverage meets target threshold (typically 80%+)

      Generate coverage report from test runner (npm test -- --coverage)Run coverageanalyzer.py on LCOV/JSON/XML reportReview prioritized gaps (P0/P1/P2)

    Permission review

    Static risk signals and limitations

    No configured static risk pattern was detected

    This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score84/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars82SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    aAAaqwq/AGI-Super-Team
    Skill path
    skills/tdd-guide/SKILL.md
    Commit
    a1b3bf19948a6f3da84347c920a23fc2799d8824
    License
    MIT
    Collected
    2026-08-04
    Default branch
    main
    View the original SKILL.md

    TDD Guide

    Test-driven development skill for generating tests, analyzing coverage, and guiding red-green-refactor workflows across Jest, Pytest, JUnit, and Vitest.

    Table of Contents

    Capabilities

    CapabilityDescription
    Test GenerationConvert requirements or code into test cases with proper structure
    Coverage AnalysisParse LCOV/JSON/XML reports, identify gaps, prioritize fixes
    TDD WorkflowGuide red-green-refactor cycles with validation
    Framework AdaptersGenerate tests for Jest, Pytest, JUnit, Vitest, Mocha
    Quality ScoringAssess test isolation, assertions, naming, detect test smells
    Fixture GenerationCreate realistic test data, mocks, and factories

    Workflows

    Generate Tests from Code

    1. Provide source code (TypeScript, JavaScript, Python, Java)
    2. Specify target framework (Jest, Pytest, JUnit, Vitest)
    3. Run test_generator.py with requirements
    4. Review generated test stubs
    5. Validation: Tests compile and cover happy path, error cases, edge cases

    Analyze Coverage Gaps

    1. Generate coverage report from test runner (npm test -- --coverage)
    2. Run coverage_analyzer.py on LCOV/JSON/XML report
    3. Review prioritized gaps (P0/P1/P2)
    4. Generate missing tests for uncovered paths
    5. Validation: Coverage meets target threshold (typically 80%+)

    TDD New Feature

    1. Write failing test first (RED)
    2. Run tdd_workflow.py --phase red to validate
    3. Implement minimal code to pass (GREEN)
    4. Run tdd_workflow.py --phase green to validate
    5. Refactor while keeping tests green (REFACTOR)
    6. Validation: All tests pass after each cycle

    Tools

    ToolPurposeUsage
    test_generator.pyGenerate test cases from code/requirementspython scripts/test_generator.py --input source.py --framework pytest
    coverage_analyzer.pyParse and analyze coverage reportspython scripts/coverage_analyzer.py --report lcov.info --threshold 80
    tdd_workflow.pyGuide red-green-refactor cyclespython scripts/tdd_workflow.py --phase red --test test_auth.py
    framework_adapter.pyConvert tests between frameworkspython scripts/framework_adapter.py --from jest --to pytest
    fixture_generator.pyGenerate test data and mockspython scripts/fixture_generator.py --entity User --count 5
    metrics_calculator.pyCalculate test quality metricspython scripts/metrics_calculator.py --tests tests/
    format_detector.pyDetect language and frameworkpython scripts/format_detector.py --file source.ts
    output_formatter.pyFormat output for CLI/desktop/CIpython scripts/output_formatter.py --format markdown

    Input Requirements

    For Test Generation:

    • Source code (file path or pasted content)
    • Target framework (Jest, Pytest, JUnit, Vitest)
    • Coverage scope (unit, integration, edge cases)

    For Coverage Analysis:

    • Coverage report file (LCOV, JSON, or XML format)
    • Optional: Source code for context
    • Optional: Target threshold percentage

    For TDD Workflow:

    • Feature requirements or user story
    • Current phase (RED, GREEN, REFACTOR)
    • Test code and implementation status

    Limitations

    ScopeDetails
    Unit test focusIntegration and E2E tests require different patterns
    Static analysisCannot execute tests or measure runtime behavior
    Language supportBest for TypeScript, JavaScript, Python, Java
    Report formatsLCOV, JSON, XML only; other formats need conversion
    Generated testsProvide scaffolding; require human review for complex logic

    When to use other tools:

    • E2E testing: Playwright, Cypress, Selenium
    • Performance testing: k6, JMeter, Locust
    • Security testing: OWASP ZAP, Burp Suite

    Alternatives

    Compare before choosing

    Computed 9323,781

    alirezarezvani/claude-skills

    tdd-guide

    Test-driven development skill for writing unit tests, generating test fixtures and mocks, analyzing coverage gaps, and guiding red-green-refactor workflows across Jest, Pytest, JUnit, Vitest, and Mocha. Use when the user asks to write tests, improve test coverage, practice TDD, generate mocks or stubs, or mentions testing frameworks like Jest, pytest, or JUnit.

    2026-07-170 platforms
    Computed 974,922

    dotnet/skills

    test-tagging

    Analyzes test suites in any language and tags each test with standardized traits (positive, negative, critical-path, boundary, smoke, regression, integration, performance, security). Use when the user wants to categorize, audit, or label tests with traits. Works across .NET (MSTest/xUnit/NUnit/TUnit), Python (pytest), TS/JS (Jest/Vitest), Java, Go, Ruby, Rust, Swift, Kotlin, PowerShell, and C++ — auto-editing when the framework has canonical tag syntax, otherwise report-only. Do not use for writ

    2026-08-040 platforms
    Computed 9532,606

    K-Dense-AI/scientific-agent-skills

    simpy

    Build, inspect, test, and analyze bounded process-based discrete-event simulations with SimPy, including events, resources, interrupts, monitoring, replications, warm-up, and reproducible output analysis.

    2026-08-030 platforms
    Computed 954,922

    dotnet/skills

    find-untested-sources

    MANDATORY for static requests to find, identify, or list untested source files or modules, sources without tests, source-to-test pairing, test-gap worklists, or suggested test locations. Invoke even for a tiny package; do not substitute manual globbing. Uses Roslyn for C#/.NET and tree-sitter for Python, TS/JS, Go, Java, Rust, and Ruby. DO NOT USE FOR: line/branch coverage, CRAP risk, or grading existing tests.

    2026-08-040 platforms