Detect and fix context leaks in code comments and documentation.
npx skills add https://github.com/gweslab/cerf --skill leak-gweslab
Please help me install this Agent Skill. Skill: leak Source: https://github.com/gweslab/cerf/tree/main/.claude/skills/leak Command: npx skills add https://github.com/gweslab/cerf --skill leak-gweslab
This Skill helps developers identify and correct narration leaks in code comments and documentation, ensuring that only technical information remains, improving code readability and maintainability.
/leak command, the Skill will analyze the codebase and provide a report on all leaks, along with instructions for fixing them.Run the command /leak to identify and fix context leaks in your codebase.
High-intent search queries and answers about installing and using this skill.
To identify and fix context leaks in code comments and documentation, run the `/leak` command to analyze your codebase, enumerate leaking text with file and line details, and rewrite or delete non-self-contained narrative.
A narration leak in code and documentation is inadvertently committed session or conversation context that lacks self-contained technical value, reducing code readability and maintainability by embedding irrelevant chat history into codebase files.
Remove session conversation context from committed code comments by running an analysis tool to detect narrative leaks, then follow provided instructions to delete the excess narration or rewrite it to be self-contained technical information.
Yes, you can detect documentation context leaks without specifying file paths or dependencies, as the analysis script automatically scans the codebase to enumerate all instances of non-self-contained narrative and provides exact file and line locations.
The best way to clean up non-technical narrative in a codebase is to use an automated detection script that enumerates context leaks by file and line number, then rewrite or delete the excess narration to ensure only self-contained technical information remains.
brittAnalyzes project codebase structure, architecture, key files, and dependencies via filesystem scanning tools.
dopiotrekRemove redundant code comments while preserving architectural explanations.
mthinesAnalyze code diffs and documentation updates to identify quality issues.
insightwavesmithAnalyze code changes to identify those meeting evidence-shape-check criteria.