Block unimplemented stub idioms in code during PostToolUse Edit|Write.
npx skills add https://github.com/youssefKadaouiAbbassi/yka-code --skill stub-warn
Please help me install this Agent Skill. Skill: stub-warn Source: https://github.com/youssefKadaouiAbbassi/yka-code/tree/main/forge/plugin/skills/stub-warn Command: npx skills add https://github.com/youssefKadaouiAbbassi/yka-code --skill stub-warn
Prevents unimplemented stubs from reaching the shipping codebase, maintaining code quality and ensuring features are implemented.
throw new Error("TODO") in TS/JS, todo!() in Rust).Activate the stub-warn hook to begin automatically blocking unimplemented stubs in your codebase.
High-intent search queries and answers about installing and using this skill.
You can block unimplemented stubs by activating a PostToolUse Edit|Write hook that automatically monitors codebase changes. This prevents stub idioms from being committed, ensuring code quality and continuous progress in collaborative environments.
Common stub idioms include `throw new Error("TODO")` in TypeScript and JavaScript, or `todo!()` in Rust. Language-specific checks recognize these patterns to automatically block unimplemented code across multi-language projects.
Prevent placeholder code from reaching production by enforcing a PostToolUse Edit|Write hook that blocks stub idioms. This ensures all placeholder markers are replaced with real functionality before code progresses further in the development pipeline.
Yes, stub blocking works for multi-language development environments by applying language-specific checks. It recognizes distinct unimplemented code idioms across various programming languages to enforce a clean codebase across the entire project.
Use automated codebase monitoring for stub blocking in collaborative development environments where maintaining code quality is critical. It ensures continuous code progress by automatically catching unimplemented stubs during every Edit or Write operation.
faisalanjumVerify that a PostToolUse hook fires once for a Write matcher.
aniruddh2003Run static analysis tools to detect security vulnerabilities, type errors, and linting issues.
skylarsaboBisect version control history to isolate regression-introducing commits and generate reports.
vinaykumarvkScan codebases for security flaws, quality issues, and accessibility violations.