القائمة
Consume BranchContextPlugin injections in commands. Use when a command depends on an injected <branch-context> block for its scope.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | branch-context-consumer |
| description | Consume BranchContextPlugin injections in commands. Use when a command depends on an injected <branch-context> block for its scope. |
Standard contract for commands that depend on BranchContextPlugin injecting a <branch-context> block before execution.
<branch-context> block.<branch-context> is absent, do not run git fallback commands; stop and report that BranchContextPlugin did not inject context for this command.Use when the command only needs the changed-file scope.
<work-scope> section in this order: unstaged, staged, then branch diff.<work-scope> to identify the scope before reading specific files.Use when the command needs branch identity, status, PR state, or the full snapshot.
<branch-metadata><status><work-scope> (unstaged, staged, then branch diff)<pull-request><warnings>Include scope source used (BranchContextPlugin context) in the command's final report.
Execute broad changes one coherent, independently verifiable stage at a time. Use when work spans multiple independently reviewable changes, or when contracts, producer-consumer migrations, generated artefacts, or release packaging create an ordered multi-stage rollout; skip small single-purpose changes.
Commit workflow using the dot git-commit gateway in the maintainer's concise one-line style. Use only after the user explicitly requests a commit or push, including /commit or /commit-push. Never infer repeat authorisation from an earlier commit or push; never run raw git commit.
Patterns for working with git branches, remotes, diffs against the default branch, and rebases. Use when resolving rebase conflicts, continuing interactive rebases, amending commits, or any git operation that would open an interactive editor.
Investigate a topic against primary sources and return cited findings, comparing credible maintainer and contributor perspectives when judgement is involved. Use when the user wants a topic researched, docs, API, or spec facts gathered, an external library or GitHub behaviour verified, competing views compared, or reading legwork delegated to a background agent.
Ask minimal clarifying questions only when ambiguity materially changes implementation. Use for routine underspecification; do not use for user-requested light or full grilling, plan stress-testing, or broad design interviews.
Stress-test a plan or proposed change through focused one-question-at-a-time grilling, with light and full intensity. Use when the user says grill, grill me, grill me lightly, ask me a couple of questions, stress-test this plan, or wants question-led scrutiny before planning.