commit

Step 1: Require Commit Config

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "commit" with this command: npx skills add kvnwolf/devtools/kvnwolf-devtools-commit

Commit

Step 1: Require Commit Config

Check if .agents/commit.config.yml exists.

  • If exists, continue to step 2

  • If not, follow references/config-setup.md to create it, then continue

Step 2: Gather Context

Run each command separately:

  • git diff --staged

  • Only if step 1 had NO output: git diff

  • git log --oneline

Step 3: Determine Staging

  • If git diff --staged has output -> use as-is (user curated manually)

  • If empty -> run git add -A to stage everything

Step 4: Sync Documentation

  • Read files from .agents/commit.config.yml

  • Find staged *.md files not in the config that could be documentation (excluding skills/ ), detect their update condition, register them

  • For each tracked file, evaluate whether update_when is met by staged changes

  • Read and update every file whose condition is met

  • If new files were registered in step 2, persist the updated config

Step 5: Stage Documentation

git add <updated-doc-files>

Step 6: Generate and Execute Commit

Subject: semantic commit format (feat: , fix: , refactor: , docs: , chore: , test: , ci: , perf: , style: , build: ). Lowercase imperative, no period, max 70 chars. Use scope when it adds clarity.

Body: explain why — motivation, trade-offs, decisions. State breaking changes explicitly.

References: issue/ticket refs on their own line (e.g., Closes #142 ).

Execute with HEREDOC:

git commit -m "$(cat <<'EOF' feat: subject line describing what changed

Body explaining why this change was made.

Closes #issue (if applicable) EOF )"

Step 7: Push

git push -u origin HEAD

Step 8: Pull Request

Only if branch was pushed in step 7.

  • Run git branch — if on main , stop

  • Generate PR title and body: git log <base-branch>..HEAD --oneline git diff <base-branch>...HEAD

  • Create PR: gh pr create --title "<title>" --body "$(cat <<'EOF'

Summary

<bullet points from commit analysis>

Test plan

<checklist> EOF )"

Acceptance checklist

  • Commit config exists at .agents/commit.config.yml

  • Documentation synced with staged changes

  • Commit message follows semantic format with body

  • Changes pushed to remote

  • PR created (if not on main)

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

unit-testing

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

convex

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

e2e-testing

No summary provided by upstream source.

Repository SourceNeeds Review