القائمة
Ensures failures in test, build, or command output are never dismissed as "pre-existing", "unrelated", or "not my problem" — they get acknowledged with an offer to fix. Auto-invoke when reporting test results, build output, CI logs, or any command output containing errors or failures.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use fff MCP / Grep / Read / Glob — never Bash grep/cat/find/head/tail/sed/awk/rg/wc — for file search and read. Use jq for JSON parsing/shaping (not node -e / python -c). A hook hard-blocks the banned Bash calls, and the dedicated tools return clean, cacheable, line-numbered results. Auto-invoke when searching, reading, or counting in files.
Planning and problem-solving discipline: enter plan mode first, write plans in the plan file (not chat), structured research, validation, implementation. Auto-invoke when the user says "plan", "make a plan", or when fixing issues or implementing features.
Use before any action: five-question self-check that catches destructive ops, scope creep, fabrication, premature completion, and ignored instructions. Auto-invoke before executing commands, editing files, or answering factual questions.
Reconcile skill collections, backport from ~/.claude/skills into a marketplace plugins tree, scrubbing proprietary refs. Use when local has diverged from upstream, or when promoting local-only skills to a marketplace.
Communication and scope discipline: how to interact with the user, handle rejection, stay in scope. Always active.
Final checklist before declaring any task complete. Auto-invoke before saying "done", "ready", "complete", or asking to commit/push.
| name | asshole |
| description | Ensures failures in test, build, or command output are never dismissed as "pre-existing", "unrelated", or "not my problem" — they get acknowledged with an offer to fix. Auto-invoke when reporting test results, build output, CI logs, or any command output containing errors or failures. |
| user-invocable | true |
You just dismissed pre-existing failures instead of offering to fix them. That's unhelpful.
When you report test results, build output, or any command output that contains errors or failures — even ones you didn't cause — you MUST:
The user hired you to help with the whole project, not just the one thing you touched.
