القائمة
Use when encountering bugs, test failures, or unexpected behavior. Hypothesis-driven debugging.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when working with git operations including commits, branches, worktrees, and PRs. Covers the full git workflow from feature isolation to PR submission.
Complete PR submission pipeline with local sub-agent review before pushing, CI verification, and automated review integration. Always dispatches code-reviewer and code-simplifier for code changes, plus conditional reviewers (security, performance, dependency, accessibility, i18n, type-design, etc.) based on change type. Waits for CI with `gh pr checks --watch`. Integrates CodeRabbit and Greptile feedback.
GitHub CLI patterns for PR reviews, comments, and API operations. Use when working with gh api commands, especially for review threads and comments.
Use when following a written plan or task list. Checkpoint verification at each step. Triggers - execute plan, follow plan, implement plan, next step, continue, proceed.
Use for parallel branch development with workspace isolation.
Use when implementing analytics, event tracking, or setting up dashboards. Covers privacy-first tracking, event patterns, and common analytics tools.
| name | debug |
| description | Use when encountering bugs, test failures, or unexpected behavior. Hypothesis-driven debugging. |
Iron Law: NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST.
1. REPRODUCE -> Trigger consistently
2. INVESTIGATE -> Gather evidence, trace data flow
3. HYPOTHESIZE -> Form ONE specific theory
4. TEST -> Minimal change to verify
5. FIX -> Address root cause
6. VERIFY -> Confirm with test
npm test -- --testPathPattern="auth"
# Document: exact steps, expected vs actual, full error message
Cannot reproduce? Gather more data. Don't guess.
git diff HEAD~5echo "=== Input to component: $INPUT ==="
# component does its thing
echo "=== Output: $OUTPUT ==="
Goal: Find WHERE it breaks, not just WHAT breaks.
Form ONE specific theory:
"Token is null because login returns before API response completes."
Not: "Something's wrong with auth" (too vague)
Smallest possible change:
console.log('Token before return:', token);
| Symptom | Wrong Fix | Right Fix |
|---|---|---|
| Null pointer | Add null check | Fix why it's null |
| Timeout | Increase timeout | Fix why it's slow |
Write test that fails before fix, passes after. Proves fix works.
| Situation | Action |
|---|---|
| Cannot reproduce | More data. Don't guess. |
| 3+ failed attempts | Question architecture. Discuss with user. |
| "Quick fix" obvious | STOP. Follow process anyway. |
Pairs with: tdd (write failing test), verification (prove fix works)