Menu
Checks if code changes require documentation updates
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Debug a Kurtosis devnet that is not producing blocks. Iterates through logs → code correlation → fix → rebuild → retest until the chain advances.
Launch a team of 4 parallel agents to add depth across multiple packages. Each agent creates 2 source files + 2 test files in non-overlapping packages. All files build and pass tests before committing.
Reviews code changes for bugs, security issues, and quality problems
Generate a minimal security patch for a specific vulnerability finding. Produces a .patch file with the smallest code change needed to remediate the issue without altering unrelated logic.
Run a comprehensive security scan on a codebase using available security scanners (Semgrep, Bandit, Trivy, osv-scanner). Returns structured findings with severity, file location, and OWASP mapping.
Generate a comprehensive security report with executive summary, detailed findings, remediation roadmap, and compliance mapping. Supports markdown and HTML output.
| name | doc-check |
| description | Checks if code changes require documentation updates |
Review code changes and determine if documentation updates or new documentation is needed.
Get the code changes - Use the method provided in the prompt, or if none specified:
gh pr diff <PR_NUMBER>git diff main or git diff --stagedgit diff main...<branch>Understand the scope - Consider what changed:
Search the docs for related content in docs/
Decide what's needed:
Report findings - Use the method provided in the prompt, or if none specified, summarize findings directly