القائمة
Use when asked to quickly stage all current changes and commit them with an automatically selected commit message.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
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.
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.
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.
Use when asked to create, rewrite, audit, or maintain README, ARCHITECTURE, CONTRIBUTING, TUTORIAL, docs navigation, project options, badges, or documentation signatures.
| name | fast-commit |
| description | Use when asked to quickly stage all current changes and commit them with an automatically selected commit message. |
Stage all current changes, analyze the diff, generate three commit message candidates, choose the best one, and commit without asking the user to pick.
Stage untracked, modified, and deleted files:
git add -A
Read the staged diff before writing the commit message:
git diff --cached
git status --short
Identify:
Generate exactly three candidates. Each candidate has:
<gitmoji_code> <type>(<scope>): <subject>.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>`
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.
| 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. |