record-quality-baseline
Record quality metrics baseline before refactoring or major changes, capturing audit scores, test coverage, and complexity for comparison
Security Assessment
About record-quality-baseline
The 'record-quality-baseline' skill is designed to capture and document key code quality metrics before making significant changes to a project. By recording test results, coverage, audit scores, TypeScript errors, and code complexity, it provides a benchmark for comparison after refactoring or implementing major changes. This allows developers to ensure that code improvements, whether they involve restructuring or reducing technical debt, do not negatively impact code quality. By capturing this baseline, teams can confidently assess whether refactoring has improved or maintained quality standards.
FAQ
What does the 'record-quality-baseline' skill capture?
The skill captures key code quality metrics including test status, coverage, audit scores, TypeScript errors, and code complexity.
When should I use this skill?
It should be used before refactoring, code restructuring, simplifying, reducing technical debt, setting quality improvement targets, or implementing major features.
Is there any specific tool required to use this skill?
The skill requires tools like npm for testing, jq for parsing coverage, and optionally TypeScript and complexity analysis tools for error checking and code complexity analysis.
Can I use this skill without TypeScript or a complexity analysis tool?
Yes, the skill can run without TypeScript and complexity analysis, but those steps will be skipped if the respective tools are not available.
What happens if the audit tool is not available?
If the audit tool is not available, the skill will inform you that the audit is not possible, but the rest of the baseline recording will proceed.
Install record-quality-baseline
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
BerryKuipers/claude-code-toolkit