Edit code comments to remove noise and add boundary and rationale notes.
npx skills add https://github.com/ylxmf2005/AgentCorp --skill comment-optimizer
Please help me install this Agent Skill. Skill: comment-optimizer Source: https://github.com/ylxmf2005/AgentCorp/tree/main/agentcorp/comment-optimizer Command: npx skills add https://github.com/ylxmf2005/AgentCorp --skill comment-optimizer
Comments in code often restate, narrate investigation, or include boilerplate, obscuring the real boundaries and why decisions matter. This skill fixes comments directly, adding why/boundary/history notes and removing noise to improve maintainability.
Run the optimizer on the current diff to prune noisy comments and insert why/boundary notes.
High-intent search queries and answers about installing and using this skill.
To fix noisy code comments, you need to identify statements that narrate investigation or decorate without adding context, then rewrite them to express boundaries, rationale, and historical context while removing restatements.
The best way to update stale comments during a code refactor is to analyze the current diff, identify missing boundary notes, and rewrite or remove the outdated comments to ensure they explain why decisions matter for future maintainers.
Code comments improve maintainability and knowledge transfer by moving beyond code restatements to document boundaries, rationale, and historical context, helping future developers understand decisions without guessing.
Yes, you can optimize comments directly across your working tree by scanning the current diff to prune noisy boilerplate and automatically insert concise why, boundary, and history notes.
You should remove comments instead of rewriting them when they consist entirely of fluff, boilerplate, or investigation narration that obscures code boundaries without stating any historical context or rationale.
t-miura-024Analyze git repository changes and retrieve detailed diffs for modified files.
ZdenekMAnalyze thesis implementation code for architecture, maintainability, and runtime risks.
el-feoAnalyze Ruby code with RubyCritic to detect smells and complexity.
Chang-Shih-YungAggregate type checker, linter, and test results into a 0-10 composite score.
