Menu
Stage and commit current session changes with a proper conventional commit message. No push.
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
| name | commit |
| description | Stage and commit current session changes with a proper conventional commit message. No push. |
| tags | ["commit","git","pre-commit","commit-message"] |
Stage and commit the current session's changes with a well-formed commit message.
Gather state (parallel):
git status (never -uall)git diff + git diff --staged to see all changesgit log --oneline -5 for recent commit styleAnalyze changes:
.env, credentials, keys)Draft commit message:
type: concise description (under 72 chars)feat, fix, refactor, docs, test, chore, styleCo-Authored-By trailerStage + commit (sequential):
git add specific files (not git add . or git add -A)git status after to verifyReport: Show the commit hash and summary. Do NOT push.
cd — working directory is already correct.--no-verify or skip hooks.Cross-reference project docs for drift, stale references, and contradictions. Outputs timestamped report. Universal baseline — works with any docs/ structure from sp-bootstrap.
Use when a non-trivial decision needs deep deliberation grounded in the project's full canonical context. Loads all canonical project docs, states the frame (target user, binding constraints, what's already decided), then enters open conversation with the user. This is a context-loading skill, not an output-producing one.
Scan frontend code for domain logic that violates Frontend=Intent, Backend=Logic. Outputs structured violation report. Universal baseline — extend with project-specific patterns.
Use when caller wants to observe how a stranger encounters a flow, artifact, or sandbox — triggers like "simulate a user journey", "test our onboarding / checkout / signup", "will my ICP convert", "how does a cold reader experience this README", "first-time user test", "cognitive walkthrough", or any request to evaluate friction from a non-builder perspective.
Absorb one or more feature branches into the base branch. Recommends merge vs rebase per branch. Designed for lazy absorption of parallel Claude session branches.
Scan docs/superpowers/ for active specs and plans. Show status table with cycle stage, progress, and blockers. Suggest what to tackle next. Works in any repo with the superpowers pipeline.