Identify and remove deferred, TODO, and stubbed code from codebases.
npx skills add https://github.com/gweslab/cerf --skill deferred-gweslab
Please help me install this Agent Skill. Skill: deferred Source: https://github.com/gweslab/cerf/tree/main/.claude/skills/deferred Command: npx skills add https://github.com/gweslab/cerf --skill deferred-gweslab
This Skill addresses the issue of 'deferred' as progress in code development, ensuring that every piece of code is implemented fully and correctly from the start.
Invoke /deferred when you detect lying code, such as stubs or TODO-marked functions, and the Skill will guide you through the process of deletion and full reimplementation.
High-intent search queries and answers about installing and using this skill.
To remove stubs and TODOs during code review, identify deferred code and enforce strict deletion of partial implementations. This ensures every instruction is fully implemented rather than leaving placeholder functions that misrepresent actual progress.
Lying code is deferred progress, such as stubbed functions or TODO markers, that falsely implies completeness. It undermines implementation oversight by masking unfinished work, requiring strict deletion and full reimplementation to ensure actual code completeness.
Enforce full implementation by applying strict rule adherence to eliminate deferred code. Automatically identify stubs or partial implementations, delete the non-compliant segments, and require a complete reimplementation of the intended functionality.
Yes, automated deferral detection identifies partial implementations and stubbed functions within the codebase. It enforces rule adherence by triggering a full retraction and reimplementation process for any detected code that fails to meet completeness standards.
Deferred code violates rule adherence because it breaks the principle that an instruction is always implemented fully. Stubs and TODOs represent partial implementations, requiring strict deletion to prevent non-compliant code from polluting the codebase.
Limitations of strict deletion for non-compliant code include the requirement to completely retract and reimplement deferred segments. This approach demands full reimplementation of functionality rather than allowing incremental development or temporary stubs.
marcmontecalvoAudit deferred-work ledger entries against codebase status and partition them.
Lev-itGenerate complete code outputs without truncation or placeholders.
VMRam95Reviews pull requests for architectural, security, and quality issues.
igbuendAutomates static code analysis with Semgrep to detect vulnerabilities and anti-patterns.
