iamkaf/clean-transient-comments
skills/clean-transient-comments/SKILL.md
Use when the user asks to "clean transient comments", "remove temporary comments", or remove comments that describe past changes rather than documenting current code.
development
Updated Apr 20, 2026
$ install --global
skillsauthnpx skillsauth add iamkaf/skills clean-transient-commentsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 20, 2026, 7:06 AM14.2s1 file scanned
SKILL.md
- name:
- clean-transient-comments
- description:
- Use when the user asks to "clean transient comments", "remove temporary comments", or remove comments that describe past changes rather than documenting current code.
- license:
- MIT
- version:
- 1.1.0
Remove comments that read like commit messages or dev notes about refactors.
Detection Heuristics
Flag comments that:
- Use past tense or temporal words ("now", "was", "used to", "moved", "changed", "updated", "fixed")
- Reference where code came from or went ("moved to X", "extracted from Y")
- Explain that something changed rather than why it exists
Examples to remove:
// This is now done via mixin// Moved to ItemFunctions.java// Updated to use new API
Preserve
- WHY explanations (rationale, edge cases, warnings)
- TODO/FIXME with ongoing relevance
- Ticket/issue references
- Domain logic documentation
Process
Phase 1: Scan
Scan provided paths, or default to src/, lib/, and common source files.
Phase 2: Report
List files, specific comments planned for removal with context, and rationale.
Wait for approval before removing.
Phase 3: Remove
After approval, delete flagged comments. Preserve all code structure and formatting.
Related Skills
iamkaf/security-review
development
VerifiedTrustedCommunity
Review a git diff, branch, or pull request for newly introduced, high-confidence security vulnerabilities. Use when the user asks for a security review, PR security pass, AppSec triage, exploitability check, or a low-noise audit of changed code, workflows, auth, input handling, secrets, or trust-boundary changes.
SKILL.mdUpdated May 28, 2026
iamkaf/imagegen-ui-match
testing
VerifiedTrustedCommunity
Use when implementing a UI from a visual mock and the user wants an imagegen-based compare-and-iterate workflow until the current page closely matches the target screenshot or mock. Covers browser screenshots, explicit side-by-side comparisons, imagegen visual audits, bitmap asset generation, and avoiding stale-reference mistakes.
SKILL.mdUpdated May 20, 2026
iamkaf/readme-improver
documentation
VerifiedTrustedCommunity
Transform boring, flat README files into polished, visually compelling project pages. Use when the user asks to improve, redesign, or make a README more interesting. Covers structure, copy, badges, banner images, and overall presentation. Produces GitHub-flavored Markdown that renders well on GitHub, npm, and similar platforms.
SKILL.mdUpdated Apr 21, 2026
iamkaf/vhs
tools
VerifiedTrustedCommunity
Create, edit, debug, or review Charmbracelet VHS terminal demo recordings and .tape files. Use when the task involves terminal GIFs/videos, VHS scripts, demo cassettes, CLI screencasts, reproducible terminal recordings, or converting terminal interactions into renderable tape files.
SKILL.mdUpdated Apr 20, 2026