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

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

Commencer

commit

Étoiles205

Forks38

Mis à jour24 juin 2026 à 20:03

Stage intended changes and create one Conventional Commit.

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

owainlewis

owainlewis/blueprint

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

Téléchargement

Exécuter dans Manus

SKILL.md

readonly

name	commit
description	Stage intended changes and create one Conventional Commit.
user-invocable	true
argument-hint	[optional commit message]

Commit

Create one Conventional Commit for the intended current changes.

Workflow

Inspect git status, git diff, and git diff --cached.
Read recent commit messages for scopes and local phrasing.
If there is nothing worth committing, stop.
Stage only intended files.
Use the user's message if provided. Otherwise write a Conventional Commit message: type(scope): subject. Imperative subject, 72 characters or fewer, no trailing period.
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.
Never bypass hooks with --no-verify. If a hook fails, fix the cause or stop and report.

Plus depuis ce dépôt

même dépôt

plan

owainlewis/blueprint

Break a spec, brief, issue tracker item, or user request into agent-sized tasks, using phases and milestones only when they clarify larger work, delivered to exactly one destination.

2026-06-29205

bootstrap-project

owainlewis/blueprint

Bootstrap a new or empty project repository with a local skeleton: README, license, .gitignore, AGENTS.md, docs, and optional commit or push only when explicit. Interview the repo creator when file-changing decisions are unclear.

2026-06-24205

branch

owainlewis/blueprint

Create a traceable Git branch for the current task.

2026-06-24205

browser-verify

owainlewis/blueprint

Verify browser-rendered work in a real browser. Use for HTML, UI, visual docs, presentations, local apps, and browser-facing changes.

2026-06-24205

debug

owainlewis/blueprint

Find and fix the root cause when something breaks: a failing test, a broken build, a bug report, or behavior that doesn't match expectations. Use when the user says 'debug', 'why is this failing', 'fix this bug', or when a failure interrupts other work.

2026-06-24205

design-doc

owainlewis/blueprint

Write a lightweight technical design document for ambiguous or consequential architecture decisions before implementation.

2026-06-24205

name	commit
description	Stage intended changes and create one Conventional Commit.
user-invocable	true
argument-hint	[optional commit message]

Commit

Create one Conventional Commit for the intended current changes.

Workflow

Inspect git status, git diff, and git diff --cached.
Read recent commit messages for scopes and local phrasing.
If there is nothing worth committing, stop.
Stage only intended files.
Use the user's message if provided. Otherwise write a Conventional Commit message: type(scope): subject. Imperative subject, 72 characters or fewer, no trailing period.
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.
Never bypass hooks with --no-verify. If a hook fails, fix the cause or stop and report.