القائمة
Use when implementation tasks are complete and final verification, commit summary, changed-file summary, and residual risk summary are needed
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when starting a new project from scratch or establishing project operating contracts, root CONTEXT.md, stack decisions, architecture summary, domain language, and a high-level roadmap before feature brainstorming
Use when executing implementation plans with mostly independent tasks in a fresh or same session after written plan approval
Use when an approved local design spec exists and an exact implementation plan is needed before code changes
Use when starting a conversation to route new-project setup requests to project-setup and make/build/create/implement app, site, tool, component, UI, API, workflow, or behavior requests to brainstorming before frontend, design, framework, or implementation skills
Use before make/build/create/implement requests for apps, sites, tools, components, UI, APIs, workflows, feature work, architecture changes, behavior changes, or unclear requirements; writes a local design spec before planning or coding
Use when executing written implementation plans linearly after written plan approval
| name | finishing-a-development-branch |
| description | Use when implementation tasks are complete and final verification, commit summary, changed-file summary, and residual risk summary are needed |
Verify the work and summarize it. Do not push, merge, open a PR, or discard work unless the user explicitly asks.
git status --short.docs/superpowers/** is not staged.If the user explicitly asks to push, merge, open a PR, or discard work, handle that request directly with normal git safety checks.
Never force-push or rewrite remote history unless the user explicitly asks and confirms.