tech-debt-analysis
Analyze and address technical debt in codebases.
Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Analyze and address technical debt in codebases.
Customer reports technical problems with videos, code examples, or course materials not working.
Validate completed implementation against plan tasks and acceptance criteria. Use when: (1) Implementation is complete, (2) User wants validation before merging/shipping, (3) Quality gate check needed after implementation. Reviews ALL plan tasks for implementation correctness, test adequacy, and code quality. Produces structured feedback (approve, request changes, or comments) - does NOT fix code.
Validates and improves test coverage for code changes. Checks coverage thresholds, identifies untested code paths, and provides guidance on writing effective tests. Use after making code changes or when improving test quality.
Generate detailed executable test cases from specifications. Use when creating detailed test cases, expanding test specs, or generating TC-IDs. Triggers on keywords like "test cases", "generate tests", "detailed tests", "TC-", "executable tests".
PHP Laravel test creation specialist. Use when the user wants to create, write, or generate tests for PHP/Laravel code. Follows project conventions and ensures 100% coverage.
Designs the verification suite from requirements only — never from code. Prevents success bias. Use when building test cases in parallel with the Build Agent, after requirements are approved by the Logic Gatekeeper.
Analyze test differences between runs to identify flaky tests and consistency issues. Use to find tests that fail intermittently.
Test Engineer for quality assurance. Creates and executes automated tests. Use this skill for testing, QA, test suites, or coverage.
This skill provides guidance for writing test factories in the Packmind codebase. It should be used when creating or updating factory functions in `**/test/*Factory.ts` files to ensure realistic test data with variety.