bug-fixing
PassAudited by ClawScan on May 1, 2026.
Overview
This is a coherent instruction-only bug-fixing workflow; it can edit and run project code, but those capabilities are disclosed and aligned with its purpose.
This skill appears safe for normal use in a development repository. Before installing or invoking it, make sure you are comfortable with an agent reading and editing project files, running tests or cleanup commands, and writing bug-fix notes. Use version control and review persistent records for sensitive information.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
When used, the agent may edit project files and run local commands as part of debugging and verification.
The skill explicitly grants file-reading, file-writing, command execution, and search tools so it can perform bug fixes and verification.
allowed-tools: [read, write, execute, grep, glob]
Use it in a version-controlled workspace, review proposed edits and commands, and avoid letting it run broad or destructive commands outside the intended project.
The agent may suggest or run cleanup commands that remove generated cache files and may require restarting local services.
The reference material includes cache-cleanup commands that delete Python bytecode/cache files under the current directory; this is relevant to fixing stale-code bugs but is still a local file-deletion operation.
find . -name "*.pyc" -delete
find . -name "__pycache__" -type d -exec rm -rf {} +Confirm the working directory before running cleanup commands, and keep these operations limited to the project repository.
Project-specific bug details could persist in the skill’s knowledge files and influence future bug-fixing sessions.
The skill intentionally maintains persistent bug-fix records that may be reused in later work.
> **Purpose**: Record all bugs fixed in the current project with root cause and fix details. > **Update Rule**: MANDATORY update after every bug fix.
Keep records project-local where possible, review what is written, and do not store secrets, credentials, private customer data, or sensitive security incident details in these files.