dcjanus/prompts

Overview

This skill helps you prepare and manage git commits, pushes, branch names, and commit-message conventions. It enforces clear authorization boundaries so no write actions (commit/push) are performed without explicit user instruction. It favors Conventional Commits and Conventional Branch naming and appends a required Co-authored-by trailer when creating commits. It also prefers git switch/restore for non-destructive workspace operations.

How this skill works

When asked to create or format a commit, the skill inspects the working tree status and suggests precise, English commit messages following Conventional Commits (type(scope): short summary). It can generate branch names that match Conventional Branch patterns and produce the exact git commands to run. It will not run git commit or git push unless the user explicitly asks; for ambiguous authorization it asks for confirmation before any write operation.

When to use it

• You need a concise, Conventional-Commits compliant commit message.
• You want a recommended branch name for a new feature or fix.
• You need command-line snippets to stage, commit (with trailers), or push changes.
• You want to avoid mixing unrelated changes into one commit.
• You need help restoring or switching files/branches safely using git restore/switch.

Best practices

• Always confirm which changed files belong to the current task before staging.
• Write commit summaries in English, short and result-focused: type(scope): summary.
• Include scope when practical; omit only if none applies.
• Append: Co-authored-by: OpenAI Codex codex@openai.com as a trailer on commits.
• Prefer git switch and git restore over git checkout for switching/restoring.

Example use cases

• Generate a commit message for a bug fix: suggests 'fix(network): handle timeout on reconnect'.
• Create a branch name for a new feature: recommends 'feat/auth-refresh-token'.
• Produce the exact commands to stage files and commit with multiple message paragraphs and trailer.
• Show how to discard a single file change with git restore or unstage with git restore --staged.
• Outline the safe sequence to switch branches and push after explicit user approval.