Skip to content

fcakyon/claude-codex-settings / plugins/github-dev/skills/commit-staged

commit-staged

Unverified

This skill should be used when user asks to "commit these changes", "write commit message", "stage and commit", "create a commit", "commit staged files", or explicitly invokes "commit-staged".

Commit Staged

Complete workflow for creating commits following project standards.

When explicitly invoked with extra text, treat that text as additional context about the changes and include it in commit planning and commit messages. When session history includes findings, motivation, or rationale, include the strongest points in the commit message body instead of relying on the diff alone.

Process

First, run the /simplify skill on the staged diff and apply its findings before committing, docs-only commits included.

  1. Preferred execution

    • If subagents are available, use github-dev:commit-creator for the full workflow.
    • Pass along any extra invocation text as additional context.
    • Otherwise follow the manual steps below.
  2. Analyze staged files only

    • Check all staged files: git diff --cached --name-only
    • Read diffs: git diff --cached
    • Completely ignore unstaged changes
  3. Commit message format

    • First line: {type}: brief description (max 50 chars)
    • Types: feat, fix, refactor, docs, style, test, build
    • Use plain language. Avoid jargon, buzzwords, and repo shorthand unless an exact command or tool name is needed.
    • Use findings and motivation from session history when available.
    • Focus on 'why' not 'what'
    • 1 sentence conventional style + 1-2 short motivation/findings sentences if possible
    • For complex changes, add bullet points after blank line
  4. Message examples

    • feat: add sign-in flow
    • fix: stop duplicate jobs on save
    • docs: add skills install snippets
  5. Documentation update

    • Check README.md for:
      • New features that should be documented
      • Outdated descriptions no longer matching implementation
      • Missing setup instructions for new dependencies
    • Update as needed based on staged changes
  6. Execution

    • Commit uses HEREDOC syntax for proper formatting
    • Verify commit message has correct format
    • Don't add test plans to commit messages

Best Practices

  • Analyze staged files before writing message
  • Keep first line under 50 chars
  • Use active voice in message
  • Use simple words that still stay accurate
  • Prefer session findings over repeating raw diff details
  • One logical change per commit
  • Ensure README reflects implementation
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 463kUpdated Claude CodeCodexVerifiedInstall
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 463kUpdated Claude CodeCodexVerifiedInstall
discernment-nudgeanthropics/skillsAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.Stars: 195kUpdated Claude CodeCodexVerifiedInstall
internal-commsanthropics/skillsA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).Stars: 195kUpdated Claude CodeCodexVerifiedInstall