Stats
Actions
Tags
From blueprint
Stages intended git changes avoiding secrets and creates clear Conventional Commits like feat(scope): subject. Useful for clean, semantic commit history.
How this skill is triggered — by the user, by Claude, or both
Slash command
/blueprint:commit [optional commit message][optional commit message]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create one clear Conventional Commit for the intended current changes.
Create one clear Conventional Commit for the intended current changes.
git status, git diff, and git diff --cached.type(scope): subject..env, credentials, or keys.feat, fix, refactor, test, docs, or chore.npx claudepluginhub owainlewis/blueprint --plugin blueprintStages files safely avoiding sensitive ones, infers conventional commit type from git diff, drafts message with scope, and executes after confirmation. Use anytime like post-planning or mid-TDD.
Executes git commits with conventional commit message analysis, intelligent staging, and message generation. Use when asked to commit changes or when /commit is invoked.
Drafts Conventional Commits messages for staged git changes. Proposes a type-scoped subject line, waits for user approval, then commits.