メニュー
Create GitHub pull requests with well-crafted titles and descriptions. Use when user says "pr", "/cortex-core:pr", "create a pr", "open a pull request", "submit a pr", "make a pull request", or asks to get their changes ready for review.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Structured feature development lifecycle with phases for research, specification, planning, implementation, review, and completion. Use when user says "/cortex-core:lifecycle", "start a lifecycle", "lifecycle research/specify/plan/implement/review/complete", "start a feature lifecycle", or wants to build a non-trivial feature with structured phases.
Development entry point that analyzes requests and routes to the appropriate workflow. Use when user says "/cortex-core:dev", "what should I work on", "start working on", "dev hub", "where do I start", "next task", "what's next", or describes a feature without naming a specific skill.
Prepare a backlog item for execution by running it through Clarify → Research → Spec. Use when user says "/cortex-core:refine", "refine backlog item", "prepare for overnight", or "prepare feature for execution". Produces cortex/lifecycle/{slug}/research.md and cortex/lifecycle/{slug}/spec.md, then sets status:refined on the backlog item.
Parallel research orchestrator. Use when the user says "/cortex-core:research", "research this topic", "investigate this feature", or when /cortex-core:refine delegates its research phase. Dispatches 3–10 parallel agents across independent angles, synthesizes into research.md or conversation output.
Create git commits with consistent, well-formatted messages. Use when user says "commit", "/cortex-core:commit", "make a commit", "commit these changes", or asks to save/checkpoint their work as a git commit.
Guide the user through the morning report after an overnight session. Walks Executive Summary and report sections, collects answers to deferred questions, advances completed lifecycles to Complete, and auto-closes backlog tickets. Use when the user says "/morning-review", "morning review", or "what happened overnight".
| name | pr |
| description | Create GitHub pull requests with well-crafted titles and descriptions. Use when user says "pr", "/cortex-core:pr", "create a pr", "open a pull request", "submit a pr", "make a pull request", or asks to get their changes ready for review. |
gh repo view --json defaultBranchRef), git log --oneline <base>..HEAD, git diff --stat <base>..HEAD, git status./cortex-core:commit first) or there are no commits ahead of base. Otherwise git push -u origin HEAD if unpushed.$() in either (temp files fail sandboxed): printf the body to $TMPDIR/pr-body.md, then gh pr create --title "..." --body-file "$TMPDIR/pr-body.md".Title: ≤70 chars, imperative, capitalized, no trailing period.
Body: a ## Summary (why it exists, where reviewers should look) and ## Changes bullets per logical change. Focus on the why and the non-obvious — the diff shows the what.
If .github/pull_request_template* exists, fill its sections instead: substitute placeholders from context, strip commented-out opt-in blocks, mark inapplicable sections N/A. {PR_NUMBER} can't resolve before creation — leave it, then gh pr edit <number> --body afterward.
No --draft/--reviewer/--assignee/--label unless asked; never --force; no AI attribution; no git -C.