Menu
Conventional commit format and guidelines. Use when creating git commits.
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.
Basé sur la classification professionnelle SOC
| name | git-commit |
| description | Conventional commit format and guidelines. Use when creating git commits. |
Always use conventional commits format: type(optional-scope): description
feat - new featurefix - bug fixdocs - documentation changesstyle - formatting, missing semicolons, etc (no code change)refactor - code change that neither fixes a bug nor adds a featureperf - performance improvementtest - adding or updating testsbuild - build system or external dependenciesci - CI configuration files and scriptschore - other changes that don't modify src or test filesrevert - revert a previous commitfeat: add dark mode toggle
fix(auth): handle expired tokens correctly
docs: update API documentation
refactor(parser): simplify token handling
test: add integration tests for payment flow
git commit -S to GPG-sign commitsDelegate tasks to other agents - pi sessions or external agents (claude, opencode, aider). Non-blocking with task tracking and completion notifications.
Git worktree conventions and commands. Use when creating, switching to, or cleaning up git worktrees for branch work.
Search past Pi coding sessions with Sesame local BM25 search. Use for multi-word session search, tool-call searches, and recent session discovery.
Interview the user relentlessly to expand context and surface intent, constraints, hidden assumptions, and unstated alternatives. Use whenever the user invokes `/grill-me`, says "grill me", "interview me", "pressure-test this", "help me think through", or whenever the user's first message is more decision than task — across coding, business, marketing, personal branding, SOPs, systems thinking, process design, and tough decisions.
Interact with local Chrome browser session (only on explicit user approval after being asked to inspect, debug, or interact with a page open in Chrome)
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.