Skip to content

dirien/yet-another-agent-harness / .claude/skills/commit

Atomic, semantic-boundary git commit workflow

/commit — Atomic Commit Workflow

When to use

When the user runs /commit or asks to commit changes.

Steps

  1. Run git status and git diff --staged to understand what's changed
  2. If nothing is staged, identify logical change groups and stage them separately
  3. Write a commit message following Conventional Commits:
    • feat: new feature
    • fix: bug fix
    • refactor: code restructuring
    • docs: documentation
    • test: tests
    • chore: tooling/build
  4. Use the imperative mood in the subject line
  5. Keep subject under 72 characters
  6. Add body with "why" not "what" if the change isn't self-evident
  7. Create the commit using a heredoc for the message
  8. Run git status to verify

Rules

  • NEVER use --no-verify or --amend unless explicitly asked
  • NEVER stage .env, credentials, or secret files
  • Prefer multiple small commits over one large commit
  • Each commit should compile and pass tests independently
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 117kUpdated Claude CodeCodexUnverifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 107kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 107kUpdated Claude CodeCodexVerifiedInstall