.claude/skills/fec-tdd-workflowRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
Use when implementing new observable frontend behavior or fixing a behavior-changing bug where a failing test can describe the missing or incorrect behavior first. Apply to components, hooks/composables, utilities, API clients, route guards, or user workflows; pure behavior-preserving refactoring us
These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.
These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.
.claude/skills/fec-tdd-workflowRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/fec-tdd-workflowRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/fec-tdd-workflowRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.
clawhub install @bovinphang/fec-tdd-workflowclawhub inspect @bovinphang/fec-tdd-workflow --version 2.9.0This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.
The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.
sha256:7b0baa2bbcda2ce21a7cd0b35169a47a8cc781b4effdc27ea92a0f16c3e38cabLICENSEmetadata.jsonpackage.jsonREADME.mdskill-card.mdSKILL.md- Added LICENSE file to clarify legal terms. - Removed skill-card.md. - Updated documentation for clearer TDD workflow and constraints. - New description clarifies intended use (observable behavior changes only). - Added guidance for pure refactoring scenarios alongside behavior-changing changes.