Finalizes, archives, and commits completed OpenSpec work.

Install

mkdir -p .claude/skills/commit-hongding0211 && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13027" && unzip -o skill.zip -d .claude/skills/commit-hongding0211 && rm skill.zip

Installs to .claude/skills/commit-hongding0211

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Archive and sync a completed OpenSpec change, then create a Conventional Commit and push the current branch. Use when the user asks to commit, archive-and-commit, sync OpenSpec changes before committing, create a feat/fix/chore commit, or push completed OpenSpec work.
268 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Intermediate

Key capabilities

  • Select a completed OpenSpec change
  • Verify the completion status of the selected change
  • Inspect the Git working tree for relevant and unrelated changes
  • Archive and sync the OpenSpec change
  • Create a Conventional Commit message

How it works

The skill identifies a completed OpenSpec change, verifies its status, archives it, and then creates a Conventional Commit message before pushing the current branch.

Inputs & outputs

You give it
User request to commit, archive-and-commit, or push completed OpenSpec work
You get back
Archived OpenSpec change, a Git commit SHA, and a pushed branch

When to use commit

  • Archiving completed changes
  • Committing verified OpenSpec work
  • Pushing finished tasks

About commit

Verifies that an OpenSpec change is complete, archives it, and performs a Git commit using Conventional Commit standards before pushing the branch.

Archive and sync a completed OpenSpec change, then create a Conventional Commit and push the current branch. Use when the user asks to commit, archive-and-commit, sync OpenSpec changes before committing, create a feat/fix/chore commit, or push completed OpenSpec work.

When not to use it

  • When OpenSpec changes are not complete
  • When validation of an OpenSpec change fails
  • When the remote Git branch has moved and force-push is not explicitly requested

Limitations

  • Does not stage unrelated dirty files silently
  • Does not revert user changes
  • Does not force-push without explicit user request

How it compares

This workflow integrates OpenSpec change management with Git operations, ensuring that only verified and archived changes are committed and pushed.

Compared to similar skills

commit side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
commit (this skill)03moNo flagsIntermediate
resolve-conflicts818moReviewIntermediate
openspec-onboard106moReviewBeginner
codex-cli-bridge99moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry