Menu
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.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional 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.
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".
Parallel adversarial review — dispatches reviewer agents on distinct challenge angles, then synthesizes findings with an Opus agent. Use when user says "critical review", "pressure test", "adversarial review", or "challenge from multiple angles". Auto-triggers in the lifecycle for Complex + medium/high/critical features before spec approval.
| name | commit |
| description | 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. |
Create a single git commit from the current working tree changes.
Run cortex-commit-preflight for status, diff, and recent history (one JSON document); stage relevant files with git add (specific files, not -A); compose the message per the format below and commit with git commit --only -m "..." -- <the same paths>. Concurrent sessions share one git index, and a bare git commit sweeps whatever a sibling session staged — --only bounds the commit to the named paths. After committing, confirm with git show --stat HEAD that only the intended files landed. Do not push, branch, or emit conversational text — only tool calls.
A PreToolUse hook validates the message before execution; if it rejects the commit, fix the message — don't bypass it via git commit -F or an editor, which the hook can't see.
Subject: imperative mood, ~72 chars, the why over the what ("Add"/"Fix"/"Remove", never "Adds"/"Added"/"Fixes" — unenforced by the hook). Add a blank-line body only when the change needs motivation, with - bullets for multiple items.
Release-type marker drives the auto-release semver bump (default patch), alone on its own line: [release-type: minor] for a backward-compatible feature, [release-type: major] for a breaking change. Read ${CLAUDE_SKILL_DIR}/references/release-type.md for the regex, the BREAKING: fallback, precedence, and the --dry-run check.
git commit --only -m "..." [-m "..."] -- <paths> (a second -m for a multi-line body; the trailing pathspec is what makes the commit concurrency-safe); never HEREDOC or command substitution — both create temp files that fail sandboxed; never disable the sandbox.
