القائمة
5-step root cause trace for errors deep in execution. Use when the error surface is far from the actual trigger. Trace backwards from the symptom to the origin.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Auto-configure AGENTS.md and brain/ knowledge docs for a new project. Use when setting up Brain Bootstrap in a new repository. Discovers the codebase, fills in templates, and writes project-specific configuration.
Use before any new feature, component, or behavioral change — when you need to explore requirements and design before writing code. Hard gate — no code until design is approved.
Build the project and verify it compiles cleanly. Use after making changes to confirm nothing is broken before running tests. Reads the build command from brain/build.md.
Activate safety mode — review every destructive command before running. Use before working on production infrastructure, migration scripts, or any task where a typo could be catastrophic.
Generate a user-facing changelog from git commits — categorize, filter noise, translate to user language. Pass a tag or date as argument (e.g. "$changelog v1.0.0" or "$changelog 2026-01-01").
Save session state before context gets full or before ending. Writes current task state, branch, and loaded docs to brain/tasks/todo.md so the next session can resume cleanly.
| name | root-cause-trace |
| description | 5-step root cause trace for errors deep in execution. Use when the error surface is far from the actual trigger. Trace backwards from the symptom to the origin. |
Trace errors from symptom to origin in 5 steps.
# Run the failing command and capture output
<test or command> 2>&1 | head -80
Record:
Based on the stack trace, generate hypotheses from most to least likely:
For each hypothesis, write what evidence would confirm or deny it.
Starting at the error line, trace each caller:
grep -rn --color=never '<error_function>' . | head -20
Go up level by level. At each level ask: "Could this be where the wrong value was introduced?"
If the trace is long (>5 levels):
# Write a test that:
# 1. Inputs the exact triggering value
# 2. Asserts the correct output
# 3. Currently fails (red)
# Then apply the fix and verify it passes (green)
After tracing:
Root Cause: <function_name> in <file>:<line>
Trigger: <what causes this function to receive the wrong input>
Fix: <minimal change needed>
Test: <test that reproduces and verifies the fix>