Use when asked to add a Changesets release note, create a .changeset markdown file, choose semver impact, or satisfy a missing changeset check before a pull request.

2026-06-280

JiangWeixian/agent-metadata

Automated setup of developer-experience tooling: ESLint, clippy, rustfmt, changesets, husky, lint-staged, GitHub workflows, templates, and commitizen. Supports JS, Rust, Mixed, and Tauri projects.

2026-06-280

create-mr

JiangWeixian/agent-metadata

Use when creating a GitHub pull request or merge request from the current branch, especially when a project PR template may exist. Creates the PR with GitHub CLI, verifies it, and arranges a scheduled CI monitor so the MR/PR is followed until required checks pass or a failure needs repair.

2026-06-280

fix-ci

JiangWeixian/agent-metadata

Use when asked to inspect, debug, fix, push, or monitor failing GitHub CI for a pull request or merge request. Fetches PR/MR CI jobs with GitHub CLI (`gh`), applies `superpowers:systematic-debugging` before changing code, verifies the fix locally, pushes the branch, and creates an automation to watch reruns and repeat the fetch/fix/push loop when CI is still failing.

2026-06-280

write-docs

JiangWeixian/agent-metadata

Use when asked to create, rewrite, audit, or maintain README, ARCHITECTURE, CONTRIBUTING, TUTORIAL, docs navigation, project options, badges, or documentation signatures.

2026-06-280

name	fast-commit
description	Use when asked to quickly stage all current changes and commit them with an automatically selected commit message.

Fast Commit

Stage all current changes, analyze the diff, generate three commit message candidates, choose the best one, and commit without asking the user to pick.

Workflow

1. Stage All Changes

Stage untracked, modified, and deleted files:

git add -A

2. Analyze the Diff

Read the staged diff before writing the commit message:

git diff --cached
git status --short

Identify:

Change type.
Scope.
User-facing behavior.
Tests or docs included.
Risk or migration notes.

3. Generate Three Candidates

Generate exactly three candidates. Each candidate has:

A title of 50 characters or fewer.
Imperative mood.
czemoji format: <gitmoji_code> <type>(<scope>): <subject>.
A body wrapped at 72 characters explaining why.

Use gitmoji text codes from https://gitmoji.dev/, such as:

:sparkles: for features.
:bug: for fixes.
:memo: for documentation.
:wrench: for tooling or configuration.
:recycle: for refactors.
:white_check_mark: for tests.

Display candidates in this format:

1. **title**: `<title>`
   **body**:
   `<body lines>`

2. **title**: `<title>`
   **body**:
   `<body lines>`

3. **title**: `<title>`
   **body**:
   `<body lines>`

4. Commit

Pick the most appropriate candidate yourself. Do not ask the user.

Commit immediately:

git commit -m "<title>" -m "<body>"

Append AI co-author trailers when the matching environment is detected.

To detect opencode, check the parent process name (opencode does not export an OPENCODE env var to subprocesses):

ps -p $PPID -o comm= 2>/dev/null | grep -qx opencode

If that succeeds, append:

Co-authored-by: opencode <opencode@ai>

If CODEX_SHELL or CODEX_CI is set, append:

Co-authored-by: Codex <codex@openai.com>

Use CODEX_SHELL or CODEX_CI for Codex detection. Do not rely on CODEX_THREAD_ID; it is session metadata, not the environment signal.

Common Mistakes

Mistake	Fix
Asking the user to choose	Pick the best candidate yourself.
Committing without reading diff	Inspect `git diff --cached` first.
Using actual emoji characters	Use gitmoji text codes like `:memo:`.
Forgetting deleted files	Use `git add -A`.
Missing AI co-author trailers	Check parent process for opencode (`ps -p $PPID`), and `CODEX_SHELL`/`CODEX_CI` before committing.