القائمة
Receiving-agent protocol. Boots a new agent into the minimum correct context (select + isolate) and produces a clear next-step plan without guessing.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Short-lived feature branches; TDD + lint + merge-ready command as exit criteria before commit; push and merge to main (or user-directed flow). Do not default to asking the user to open a PR. Use when implementing a feature or non-trivial fix, when the user asks for branch/git workflow, or after substantial edits that should not stay uncommitted.
Change-aware quality pass: diff scope, readability, function size and control flow, comments where non-obvious, and alignment with project linting. Use before merge or with handoff when the user wants industry-style maintainability beyond what tests assert.
Define and maintain lightweight evaluations (acceptance criteria, regression checks, golden tests) so “green” is objective and repeatable.
Evidence-driven debugging/incident workflow: reproduce, isolate, minimize, fix, verify, and prevent regressions.
Establish lightweight release discipline: definition of merge-ready, versioning/changelog habits, and safe rollout/rollback practices.
Maintain a lightweight risk register (top risks, triggers, mitigations, rollback) to prevent scope drift and improve decision quality.
| name | context-bootstrapper |
| description | Receiving-agent protocol. Boots a new agent into the minimum correct context (select + isolate) and produces a clear next-step plan without guessing. |
Use this skill when starting work on this repo, resuming after a break, switching to a new “feature-agent”, or when context feels bloated/confusing.
Goal: reach a confident, bounded next step using minimal context.
Project baseline (always-on context)
.cursor/rules/always.mdcAGENT_HANDOFF.mdCurrent phase / feature truth (choose the one that matches the user’s goal)
PM_PLAN.md (phase/scope)TEST_PLAN.md (Tier 1 / Tier 2 validation gates)Most recent session handoff note (if present)
.cursor/handoff/NNNN-handoff-YYYY-MM-DD_HHmm.md (highest NNNN, tie-break by timestamp)doc/handoff/NNNN-HANDOFF-YYYY-MM-DD_HHmm.md (same rule)If the task is code-touching: read the smallest set of files necessary to act safely.
After reading, produce a short brief with:
If any required inputs are missing, stop and ask before acting.
Preferred context payload for a new session:
AGENT_HANDOFF.md + the relevant plan doc(s) (project state)Avoid: