Menu
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.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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. |
| inputs | [] |
| outputs | ["GitHub PR URL — created via gh pr create (printed to stdout)"] |
| preconditions | ["Must be on a feature branch with commits ahead of the base branch","No uncommitted changes in working tree","GitHub CLI (gh) installed and authenticated"] |
Create a GitHub pull request from the current branch.
git branch --show-current), base branch (gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name'), git log --oneline <base>..HEAD, git diff --stat <base>..HEAD, git status./cortex-core:commit first) or the branch has no commits ahead of base (nothing to PR); else push if unpushed: git push -u origin HEAD..github/pull_request_template.md, .github/PULL_REQUEST_TEMPLATE.md, or a file under .github/pull_request_template/ or .github/PULL_REQUEST_TEMPLATE/); if found, read ${CLAUDE_SKILL_DIR}/references/template-filling.md and follow it, otherwise use the default format below.$() in either (creates temp files that fail sandboxed): printf the body to $TMPDIR/pr-body.md, then gh pr create --title "..." --body-file "$TMPDIR/pr-body.md".## Summary
<1-3 sentences: why it exists, what reviewers should focus on>
## Changes
- <bullet per logical change — high-level, not a changelog>
Focus on the why and the non-obvious — the diff already shows the what.
Max 70 characters, imperative mood, capitalized ("Add", "Fix", "Update"), no trailing period.
No --draft/--reviewer/--assignee/--label unless requested; no --force push, ever; no AI attribution in the body; no command chaining (separate tool calls); no git -C.