commit-work
Commit Work
Commit all changes with the OpenSpec proposal title as the commit message and the change ID as a git trailer. Archives the change first if it is still active.
When to use
- The user wants to commit the current work with OpenSpec metadata attached.
- An active OpenSpec change exists and should be archived as part of committing.
- The user explicitly invokes
/commit-workor asks to "commit this change".
Steps
-
Determine OpenSpec ID and title:
- If arguments are provided, use them
- If you are currently working on an OpenSpec, use that ID and title
- Otherwise:
- Run
openspec listto find active changes - If exactly one active change exists, use that ID
- If multiple changes exist, ask the user which one to use
- If no changes exist, ask the user for the ID and title
- Extract the title from the first heading in
openspec/changes/<id>/proposal.md
- Run
-
Archive the OpenSpec change (if not already archived):
- Check if
openspec/changes/<id>/directory exists - If it exists, invoke
/opsx:archive <id> - If the directory does not exist (already archived), skip this step
- Check if
-
Run the following commands to stage all changes and create a commit with the OpenSpec ID as a git trailer:
git add -A git commit -m "<title>" --trailer "OpenSpec-Id=<openspec-id>"
Reference
- Run
git commit --helpfor commit options (see especially--trailer)
More from avantmedialtd/skills
typescript-react-standards
Opinionated TypeScript and React development standards from Avant Media. Use when scaffolding new components, reviewing code, writing TypeScript interfaces or types, setting up project structure, creating React hooks, or working on any TypeScript/React codebase. Also use when the user asks about best practices, patterns, or conventions for TypeScript or React projects, even if they don't explicitly mention "standards.
13jira
Manage Jira issues from the command line. Use when working with Jira issues, creating tasks, updating status, assigning work, linking issues, managing versions, setting or reading custom fields (Story Points, Sprint, Severity, etc.), or searching for issues.
12e2e-testing
E2E and visual regression testing with Playwright. Use when writing tests, running E2E tests, debugging test failures, or working with visual baselines. Contains test commands, patterns, and debugging tips.
10power-stack
Bun/Elysia/React/MUI monorepo stack blueprint. Use when scaffolding a new project, adding a new app or package to the monorepo, choosing dependencies, or making architectural decisions. Contains the full tech stack, conventions, and wiring patterns.
6confluence
Manage Confluence pages from the command line. Use when working with Confluence pages, spaces, comments, labels, attachments, or searching wiki content.
4start-work
Assign a Jira issue to yourself and convert it into an OpenSpec proposal. Use when the user says "start work", "pick up an issue", "take the next ticket", or provides a Jira key and wants to begin work on it. Handles issue selection from the backlog, assignment, transition to In Progress, and scaffolding an OpenSpec change with Jira context embedded in the proposal.
1