Menu
Create a meaningful git commit message based on current changes.
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.
| name | commit |
| description | Create a meaningful git commit message based on current changes. |
| argument-hint | ["issue-url | issue-id"] |
git statusgit diff HEADgit branch --show-currentAlways ensure you're on a feature branch
Always sign-off my commits with my git config user.name and user.email
Always run tests and lint the code before creating a git commit
NEVER git commit or git push without explicit user approval - ALWAYS ask first
NEVER add any agent as a co-author, only add co-author(s) when the user explicitly requests it
Create a meaningful commit message based on the current staged or unstaged changes.
Ensure it follows the Conventional Commits specification.
Use four separate headings (with newlines after each):
Avoid stating obvious facts or padding sections.
If the issue-url or issue-id ($ARGUMENTS) is provided, add Relates to $ARGUMENTS as the first line after the commit title to associate the commit to its issue. Use Linear MCP server or GitHub gh cli if available to get issue-url when issue-id is provided
Basé sur la classification professionnelle SOC
Review a PR (by link or from current context) or the current feature branch using a multi-model, verification-first workflow.
Summarize the recent work done in the current Claude context into today's Obsidian daily note (daily/YYYY-MM-DD.md), merging without duplicating. Use when the user says "obsidian daily", "log my work to obsidian", "update my daily note", or asks to record today's work into their Obsidian vault.
Create a good pull request
Pull latest main, switch to it, then assess and clean up merged branches and worktrees for a given repo
Fetch, assess, and address PR review comments — fix valid ones, explain why invalid ones are skipped, reply with commit links, and resolve threads.
GitHub Actions workflow standards for this repository. Use when reviewing or fixing GitHub Actions workflows to enforce security hardening, permissions, and operational conventions.
