Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

bp-commit

Étoiles3

Forks0

Mis à jour24 mars 2026 à 10:57

Commit current changes following emoji+type conventions with code formatting. Triggers on "/bp-commit", "/commit", "commit this", "commit changes", "save my changes", or any request to create a git commit. Also triggers on "stage and commit", "commit with message", "make a commit", "let's commit", or "save this progress". Do NOT trigger when the user also mentions pushing — route to /bp-ship instead. Runs code formatting on changed files before committing.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

skaisser

skaisser/blueprint

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name

bp-commit

description

Commit: Stage and Commit Changes

Language

Read blueprint/.config.yml → language. If auto, detect from the user's messages. All generated content MUST be in the detected language. Skill instructions stay in English — only output changes.

Commit the current changes following our conventions. Commit only — do not push to remote.

Process

Review changes: git status and git diff
Stage only necessary files (never git add -A blindly)
NEVER stage .env, .env.*, *-api-key, credentials.json, or files containing API keys/tokens
Run code formatting if the project has a formatter configured (check project conventions)
Write a concise 1-2 sentence commit message focusing on why the change was made, not just what changed
Commit with emoji format: <emoji> <type>: <description>

Emoji Types

Emoji	Type	Use
✨	feat	New features
🐛	fix	Bug fixes
📚	docs	Documentation
💄	style	Formatting
♻️	refactor	Restructuring
⚡	perf	Performance
🧪	test	Testing
🔧	build	Build changes
🧹	chore	Maintenance
📋	plan	Planning
🔒	security	Security
🗃️	migration	DB migrations
📦	deps	Dependencies
🔀	merge	Branch merges

Present tense, lowercase, atomic commits. NEVER add AI signatures.

Use $ARGUMENTS as context for the commit message if provided.

Plus depuis ce dépôt

même dépôt

flow-auto

skaisser/blueprint

Fully autonomous SDLC pipeline — zero user intervention. Opus 4.6 runs the entire workflow from plan through PR, handles review feedback loops, and stops only when the PR is ready for human merge. Use this skill whenever the user says "/flow-auto", "auto flow", "autonomous flow", "just do everything", "full auto", "hands off", "run it all", or any request to run the complete pipeline without checkpoints or user decisions. Also triggers on "no intervention", "auto pipeline", "unattended flow", "fire and forget flow", "do everything and leave me a PR", or "I'm going to sleep just build it". This is the zero-touch version of /flow — same pipeline, no pauses. IMPORTANT: never use AskUserQuestion in this skill — all decisions are made autonomously.

2026-03-273

flow-auto-wt

skaisser/blueprint

Fully autonomous SDLC pipeline in an isolated git worktree — zero user intervention, zero git conflicts with other terminals. Creates a lightweight worktree (no Herd URL, no VS Code, no SSL), runs the full flow-auto pipeline inside it, and stops when the PR is ready for merge. Use this skill whenever the user says "/flow-auto-wt", "auto flow worktree", "parallel flow-auto", "flow-auto in worktree", or any request to run the autonomous pipeline in an isolated worktree. Also triggers on "isolated flow-auto", "worktree auto", "parallel auto", "run flow-auto in isolation", "don't touch my branch", "run in parallel", "parallel pipeline", or when running multiple flow-auto instances on the same repo. IMPORTANT: never use AskUserQuestion in this skill — all decisions are made autonomously.

2026-03-273

plan

skaisser/blueprint

Create structured implementation plans with git branches and memory search. Use this skill whenever the user wants to plan a feature, fix, refactor, or any development task. Triggers on: "/plan", "plan this", "create a plan for", "let's plan", "I need to plan", "break this into phases", "how should we approach", "let's think about how to build", or any request that involves planning, phasing, or strategizing before coding. For worktree-based plans (isolated directory), use /plan-wt instead. ALWAYS use this skill before starting implementation — planning first, coding second.

2026-03-273

start

skaisser/blueprint

Initialize a new project with GitHub Actions, git hooks, blueprint workspace, CLAUDE.md, and branches. Use this skill whenever the user says "/start", "initialize project", "setup project", "start new project", or any request to set up the standard development workflow in a repo. Also triggers on "project init", "bootstrap project", "setup hooks", or "initialize repo". Sets up everything: claude-pr-reviewer.yml + tests.yml actions, commit hooks, blueprint/ workspace, CLAUDE.md, configurable staging branch. Updates are handled by `blueprint update` — no separate sync skills needed.

2026-03-273

backlog

skaisser/blueprint

Capture, manage, and promote pre-planning ideas before they become full plans. Use this skill whenever the user says "/backlog", "add to backlog", "backlog idea", "capture this idea", "save this for later", "I had an idea", or any request to manage the idea backlog. Also triggers on "list ideas", "promote idea", "backlog list", "drop idea", "mark done", "what's in the backlog", "show me the ideas", "pending ideas", or any request to add/view/promote/done/drop items in blueprint/backlog/. The backlog is the pre-planning stage — ideas live here until promoted to /plan. Even if the user doesn't explicitly say "backlog", trigger when they describe wanting to capture a feature idea, task, or improvement for later without implementing it now. This skill is the gateway to the SDLC — nothing gets planned or built without first passing through the backlog.

2026-03-263

bp-status

skaisser/blueprint

Show quick repo status — branch, base, plan, PR info in one shot. Triggers on "/bp-status", "/status", "show status", "repo status", "what branch am I on", "current status", "where am I", "project status", "what's the current state", "which branch", "is there a PR open", "what plan am I on". Uses blueprint CLI with git fallback.

2026-03-243

name

bp-commit

description

Commit: Stage and Commit Changes

Language

Commit the current changes following our conventions. Commit only — do not push to remote.

Process

Review changes: git status and git diff
Stage only necessary files (never git add -A blindly)
NEVER stage .env, .env.*, *-api-key, credentials.json, or files containing API keys/tokens
Run code formatting if the project has a formatter configured (check project conventions)
Write a concise 1-2 sentence commit message focusing on why the change was made, not just what changed
Commit with emoji format: <emoji> <type>: <description>

Emoji Types

Emoji	Type	Use
✨	feat	New features
🐛	fix	Bug fixes
📚	docs	Documentation
💄	style	Formatting
♻️	refactor	Restructuring
⚡	perf	Performance
🧪	test	Testing
🔧	build	Build changes
🧹	chore	Maintenance
📋	plan	Planning
🔒	security	Security
🗃️	migration	DB migrations
📦	deps	Dependencies
🔀	merge	Branch merges

Present tense, lowercase, atomic commits. NEVER add AI signatures.

Use $ARGUMENTS as context for the commit message if provided.