commit-changes

Generate a smart commit message from staged or unstaged changes and create a commit. Use when the user wants to commit their work with a meaningful message.

Aller à l'installation

Dépôt: kevinreber/claude-code-configs
Dernière activité de la source: 26 avril 2026 à 21:25
Langue détectée de SKILL.md: anglais
Étoiles: 1
Forks: 0

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

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.

Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.

npx skills add https://github.com/kevinreber/claude-code-configs --skill commit-changes

La commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.

Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

SKILL.md

Instructions source · Aperçu en lecture seule

Retour à la recherche Retour à l’installation

pr-pipeline

Orchestrate the full pull-request workflow end to end — pick the right mode (review an existing PR, ship new work, or respond to review comments), chain the pr-* and validate skills in the right order, converge over repeated passes, and always leave a visible trail on GitHub. Use when the user says "run the pipeline", "/pr-pipeline", "review this PR properly", "take this change all the way to a PR", or wants the standard post-change review workflow instead of invoking each skill by hand.

2026-08-19

fable

Adopt Fable-class working discipline for this session — outcome-first communication, finish-the-turn autonomy, parallel tool use, faithful reporting. Use when the user says "/fable", "fable mode", "act like fable", or wants a smaller model (Opus, Sonnet) to work with the discipline of a Mythos-class model. Also invocable from other skills as a style preamble for long or high-stakes tasks.

2026-07-09

daily-recap-v2

Full workday recap across all tools — Jira, GitHub, Slack, Confluence, Google Docs, and Claude Code activity. Stores all data in SQLite with Turso sync for remote access. For Claude-only activity tracking, use /daily-review-v2 instead.

2026-05-17

Tout voir dans ce dépôt

Commit Changes

Analyze current changes and generate a meaningful commit message following Conventional Commits specification.

Instructions

Check for changes:

Run git status to see what files have changed
If there are unstaged changes, ask user if they want to stage all or specific files

Stage files if needed:

If user wants to stage all: git add -A
If specific files: git add <files>

Analyze staged changes:

Run git diff --cached --stat to see what's staged
Run git diff --cached to see detailed changes
Analyze the changes to understand what was done

Show diff preview to user:

Run git diff --cached to get the full staged diff
Present the diff to the user so they can review exactly what will be committed
Ask if they want to proceed or make any changes before continuing

Generate commit message following Conventional Commits:

Format:

<type>(<scope>): <subject>

<body>

<footer>

Types:

feat: New feature
fix: Bug fix
docs: Documentation only
style: Formatting, missing semicolons, etc.
refactor: Code change that neither fixes a bug nor adds a feature
perf: Performance improvement
test: Adding or updating tests
chore: Maintenance tasks, dependency updates
ci: CI/CD changes
build: Build system changes

Guidelines:

Subject line: max 50 characters, imperative mood (e.g., "add", "fix", "update")
Body: wrap at 72 characters, explain what and why (not how)
Reference issues when applicable (e.g., "Closes #123", "Fixes #456")
Add Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> in footer

Present the commit message:

Suggested commit message:

feat(auth): add OAuth2 login support

Implement Google and GitHub OAuth2 providers for user authentication.
This replaces the legacy session-based auth system.

- Add OAuth2 configuration endpoints
- Implement token refresh logic
- Update user model with provider fields

Closes #123

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

Ask for approval:

Show the generated message to the user
Ask if they want to commit with this message or modify it

Create the commit:

Use HEREDOC format for proper multi-line message:

git commit -m "$(cat <<'EOF'
<commit message here>
EOF
)"

Confirm success:

Run git log -1 --oneline to show the commit was created
Display the commit hash and message

Important Notes

Always analyze the actual changes, don't guess

Subject should be clear and concise (max 50 chars)

Use imperative mood: "add feature" not "added feature"

Body should explain WHY, not just WHAT

Break down complex changes into bullet points

Always add the Co-Authored-By footer

Use HEREDOC for multi-line commit messages

If changes span multiple concerns, suggest splitting into multiple commits

Reference issue numbers when relevant (e.g., JIRA tickets, GitHub issues)

Commit Changes

Analyze current changes and generate a meaningful commit message following Conventional Commits specification.

Instructions

Check for changes:

Run git status to see what files have changed
If there are unstaged changes, ask user if they want to stage all or specific files

Stage files if needed:

If user wants to stage all: git add -A
If specific files: git add <files>

Analyze staged changes:

Run git diff --cached --stat to see what's staged
Run git diff --cached to see detailed changes
Analyze the changes to understand what was done

Show diff preview to user:

Run git diff --cached to get the full staged diff
Present the diff to the user so they can review exactly what will be committed
Ask if they want to proceed or make any changes before continuing

Generate commit message following Conventional Commits:

Format:

<type>(<scope>): <subject>

<body>

<footer>

Types:

feat: New feature
fix: Bug fix
docs: Documentation only
style: Formatting, missing semicolons, etc.
refactor: Code change that neither fixes a bug nor adds a feature
perf: Performance improvement
test: Adding or updating tests
chore: Maintenance tasks, dependency updates
ci: CI/CD changes
build: Build system changes

Guidelines:

Subject line: max 50 characters, imperative mood (e.g., "add", "fix", "update")
Body: wrap at 72 characters, explain what and why (not how)
Reference issues when applicable (e.g., "Closes #123", "Fixes #456")
Add Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> in footer

Present the commit message:

Suggested commit message:

feat(auth): add OAuth2 login support

Implement Google and GitHub OAuth2 providers for user authentication.
This replaces the legacy session-based auth system.

- Add OAuth2 configuration endpoints
- Implement token refresh logic
- Update user model with provider fields

Closes #123

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

Ask for approval:

Show the generated message to the user
Ask if they want to commit with this message or modify it

Create the commit:

Use HEREDOC format for proper multi-line message:

git commit -m "$(cat <<'EOF'
<commit message here>
EOF
)"

Confirm success:

Run git log -1 --oneline to show the commit was created
Display the commit hash and message

Important Notes

Always analyze the actual changes, don't guess

Subject should be clear and concise (max 50 chars)

Use imperative mood: "add feature" not "added feature"

Body should explain WHY, not just WHAT

Break down complex changes into bullet points

Always add the Co-Authored-By footer

Use HEREDOC for multi-line commit messages

If changes span multiple concerns, suggest splitting into multiple commits

Reference issue numbers when relevant (e.g., JIRA tickets, GitHub issues)

name	commit-changes
description	Generate a smart commit message from staged or unstaged changes and create a commit. Use when the user wants to commit their work with a meaningful message.

commit-changes

Informations de source

Options d'installation

Vérifiez les fichiers source

Plus depuis ce dépôt

Plus depuis ce dépôt

Commit Changes

Instructions

Important Notes

Commit Changes

Instructions

Important Notes