workflow-add-test-coverage
Skill18 starsChanged 36 days agoNo licenceView on GitHub
Coverage-fill workflow for untested code. Use when you have legacy/inherited Magento custom code that has no tests (or low coverage) and you want to systematically add unit + integration tests before refactoring or extending it. Process: identify target scope (a module, a class, or coverage gaps from var/coverage.xml), use mcp__pb-codegraph__find_symbol + impact to map all public methods needing coverage, build a mini-plan of test tasks per uncovered method, then invoke /hcf:plan-orchestrate to drive tdd-worker through writing characterisation tests (RED-GREEN, no behaviour change), then re-run coverage to verify. Stops at 'tests written + green + coverage improved' — does NOT touch the production code being tested. Composable: can be chained from workflow-build-feature when the build touches a file with coverage < threshold.
In this repository36 other files it gives its agents.
- agent-teamsSkill
- analyze-m1-module-for-migrationSkill
- audit-loopSkill
- billing-skillSkill
- cache-diagnosticSkill
- cavemanSkill
- code-quality-auditSkill
- create-backend-controllerSkill
- create-frontend-controllerSkill
- database-query-analysisSkill
- debt-ledgerSkill
- deploy-checkSkill
- email-theme-stylingSkill
- github-analysisSkill
- gold-buy-signalSkill
- hyva-module-compatibilitySkill
- hyva-tailwind-integrationSkill
- loki-checkoutSkill
- magecli-skillSkill
- magento2-widget-creationSkill
- magento-controller-refactorSkill
- magento-diagnosticSkill
- manual-test-planSkill
- page-banner-setupSkill
- publish-test-reportsSkill
- security-scanSkill
- server-scanSkill
- status-page-monitoringSkill
- uat-deploy-verifySkill
- verify-featureSkill
- wiki-docsSkill
- workflow-build-featureSkill
- workflow-investigate-bugSkill
- workflow-onboard-projectSkill
- workflow-security-auditSkill
- write_as_lucasSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. About 0 are common, 10 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.