Menu
Search for one unknown evidence-backed bug, then hand the reproduced defect to diagnosis. Use for bug hunts or unexplained failing validation; not an already-reported defect with a known repro.
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
Resolve short approval against the latest checkpoint. Use for "lgtm", "looks good", "approved", or "go ahead"; not risky or review feedback.
Re-check a prior assistant claim. Use when user says "nack", "not convinced", or "check again"; not for review feedback.
UI/UX routing front door. Use as the front door for broad or ambiguous UI/UX work that needs the right build, redesign, audit, design-system, accessibility, or browser specialist. Do not use when the user already names a narrower UI skill.
Proposes UI Vault resource upgrades for a selected webpage. Use when the user asks for libraries, assets, effects, or inspiration for an existing page. Do not use for implementation or greenfield design.
Upload, list, or delete files with s3upload and return expiring Azure links. Use for configured temporary Azure storage; not for S3 or cloud setup.
Ship local Git changes by inspecting, polishing, validating, split-committing, and pushing. Use for commit, push, ship, delivery audit, or delivery blockers; not deploys or releases.
| name | bug-harvest |
| description | Search for one unknown evidence-backed bug, then hand the reproduced defect to diagnosis. Use for bug hunts or unexplained failing validation; not an already-reported defect with a known repro. |
Use this as a thin, discoverable wrapper around diagnose and tdd. The job is not to scan forever; it is to find one high-confidence bug candidate, build a feedback loop, fix it, and validate it.
git status --short --branch, repo instructions, manifests, tests, and recent validation output.diagnose for the repro/fix loop.tdd only when the fix needs a new regression test or missing seam.Accept a candidate only when you can state:
Bug candidate:
- symptom:
- evidence:
- repro command or artifact:
- expected signal after fix:
- likely files:
Reject code-smell-only candidates. If no candidate has a runnable or constructible feedback signal, stop and report what evidence is missing.
git-commit-push with validation receipts.technical-auditor.Bug harvest:
- candidate:
- repro:
- fix:
- regression/validation:
- handoff or next candidate:
Follow the shared skill contract for repo study, dirty-worktree hygiene, verification evidence, safe handoffs, and safety defaults.