Skip to main content

/

/

Stats

Actions

Tags

Stats

Actions

Tags

ClaudePluginHub

Community directory for discovering and installing Claude Code plugins.

Find plugins for your stack

Instant recommendations from directory engagement — install-command copy activity and component reuse.

Product

Browse Plugins
Marketplaces
Pricing
About
Contact

Resources

Learning Center
Blog
Weekly Digest
Claude Code Docs
Plugin Guide
Plugin Reference
Plugin Marketplaces

Community

Browse on GitHub
Get Support

Legal

Terms of Service
Privacy Policy

Browse · Plugins · Top Plugins · Marketplaces · Components · Technologies · Skills · Agents · Commands · Hooks · MCP Servers · LSP Servers · Output Styles · Themes · Monitors

Categories · Productivity · Development · Testing · Deployment · Security · Documentation · Data · Utilities

© 2025 ClaudePluginHub

Community Maintained · Not affiliated with Anthropic

ClaudePluginHub

ClaudePluginHub

Tools Learn Pricing

Search everything...

commit | blueprint

Home
Skills
blueprint
commit

Skill

commit

Stages intended git changes avoiding secrets and creates clear Conventional Commits like feat(scope): subject. Useful for clean, semantic commit history.

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/blueprint:commit [optional commit message]

User invocable

Model invocable

Inline context

Default effort

Argument hint[optional commit message]

Context Preview

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.

SKILL.md

28 lines · ~241 tokens

Stats

LanguageShell

Stars0

MaintenanceExcellent

Last CommitMay 14, 2026

Actions

View Source View Plugin View on GitHub View README

Tags

conventional-commits

Stats

LanguageShell

Stars0

MaintenanceExcellent

Last CommitMay 14, 2026

Actions

View Source View Plugin View on GitHub View README

Tags

conventional-commits

Commit

Create one clear Conventional Commit for the intended current changes.

Workflow

Inspect git status, git diff, and git diff --cached.
Read recent commit messages for useful scopes and local phrasing.
If there is nothing worth committing, stop.
Stage only intended files. Never stage secrets.
Use the user's message if provided. Otherwise write a Conventional Commit message: type(scope): subject.
Create the commit and report the hash and message.

Rules

Prefer staging specific files over broad adds.
Do not commit .env, credentials, or keys.
If the diff is not understood, stop.
Prefer feat, fix, refactor, test, docs, or chore.
The subject should say what changed. Add a body when the why, risk, or verification matters.

Reused across plugins

3plugins reuse this skill

First indexed Jun 7, 2026

blueprint
Origin
137
blueprint0
blueprint0

ClaudePluginHub fallback·generated from the plugin's indexed repository (aldoawp/blueprint) — no native marketplace selected

$

npx claudepluginhub aldoawp/blueprint

Similar Skills

commit

137

Stages intended git changes avoiding secrets and creates clear Conventional Commits like feat(scope): subject. Useful for clean, semantic commit history.

commit

34

Stages 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.

git-commit

47

Executes git commits with conventional commit message analysis, intelligent staging, and message generation. Use when asked to commit changes or when /commit is invoked.

1 tool

View git-commit