القائمة
Git Commit Generator - Generate standardized commit messages following Conventional Commits specification
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Process one GitHub issue end-to-end — read the issue + referenced repo docs/code + existing comments, verify against the landed implementation/intent, and post evidence-backed findings as a comment on the issue. Covers doc-review, doc-audit, system-audit, research, and idea issue types. Use when handling a single issue (issue-sweep calls this per issue).
Sweep open GitHub issues for unprocessed human input and act on each via the issue-review skill — delete-PRs for human-approved deprecated docs, doc-update PRs for approved drifted docs, fix-PRs for approved bugs, analysis+TDD-plan comments for feature/design requests (then implement after confirmation), close issues whose PR merged, comment-only on conditional/security/needs-decision ones. The actionable signal may be a comment OR the issue body. With --autofix-green, also auto-fixes "green" issues that have no human reply yet (unambiguous + verifiable-here + low-risk + non-security) — reproduce→fix→test→PR, never auto-merge. Run manually (/agentloop:issue-sweep) or on a schedule. Designed for a doc-audit + spin-off + feature workflow.
One-command setup/update of an agentloop FLEET on a teammate's machine or cloud — asks a few defaulted questions, then generates/reconciles the two config files (deployment.json + repos.json) and installs the schedule. LOCAL = a crontab marker-block wiring fleet/driver.ts (one row per skill; the driver fans out to every covered repo). CLOUD = one claude routine per (repo×skill) via RemoteTrigger, batch-created from the same catalog. Idempotent — re-run to upgrade. This is the SCHEDULING side that `bootstrap` (repo adoption) deliberately leaves out. Interactive — never runs unattended.
Independent clean-context review of ONE open GitHub pull request — read PR diff + linked issue + verify every claim against live code/tests + run the verification gate (pre-merge) and diagnose its root-cause + detect conflicts with sibling PRs, then emit an evidence-backed merge-readiness verdict (MERGE / COMMENT / SUPERSEDE / BLOCK / CLOSE). Runs verification every time (read-only safe); --post writes one verdict comment. Never auto-merges (that gated step belongs to pr-sweep). Use /agentloop:pr-review <pr#> for a single PR; pr-sweep batches this engine across all open PRs.
Batch-review every open GitHub PR and drive it to a terminal state autonomously — fan out a clean-context pr-review per PR (verify claims against live code, run the verification gate), cluster PRs by shared issue + shared files, DEDUP-CLOSE same-issue duplicates (keep the best one, comment + close the twin), and GATED auto-merge every verified non-breaking PR (docs/tests/fixes AND features) while escalating only security / breaking changes / architecture-direction decisions to a human. Designed to run on a schedule on an independent machine so PRs get reviewed + merged without a human in the loop. Run /agentloop:pr-sweep (review+comment+dedup-close only), /agentloop:pr-sweep --merge (also auto-merge gated PRs), or /agentloop:pr-sweep --dry-run (report only).
Iterative clean-context review of a design/plan document or issue — spawn independent-perspective reviewers each round, score, and synthesize findings without carrying prior-round bias. Use to review an implementation plan, architecture doc, or design proposal before building.
| name | commit |
| description | Git Commit Generator - Generate standardized commit messages following Conventional Commits specification |
| allowed-tools | ["Bash","Read","Glob","Grep","AskUserQuestion"] |
Generate standardized git commit messages following the project's Conventional Commits specification.
<type>(<scope>): <subject>
<body>
<footer>
Based on project history analysis, use the following types:
| Type | Description | Example |
|---|---|---|
feat | New feature | feat: add user authentication |
fix | Bug fix | fix: resolve login timeout issue |
docs | Documentation only | docs: update API documentation |
style | Code style (formatting, semicolons, etc.) | style: fix indentation |
refactor | Code refactoring (no feature change) | refactor: extract validation logic |
perf | Performance improvement | perf: optimize database queries |
test | Add or modify tests | test: add unit tests for auth module |
chore | Build process or auxiliary tools | chore: update dependencies |
ci | CI/CD configuration | ci: add GitHub Actions workflow |
build | Build system changes | build: upgrade webpack to v5 |
Scope indicates the affected module or area, enclosed in parentheses:
feat(agentloop): add verification skill
fix(auth): resolve token refresh issue
Common scopes in this project:
agentloop, blocklet, arcblock-contextblocklet-dev-setup, blocklet-prGood examples:
feat: add blocklet-branch skill for branch managementfix: resolve gh command order issuedocs: update installation guideBad examples:
feat: Added new feature. (wrong tense, has period)Fix bug (missing type prefix)feat: This commit adds a new feature that... (too verbose)Closes #123BREAKING CHANGE: descriptionWhen user requests to create a commit:
git status
git diff --staged
git diff
IMPORTANT: If there are unstaged changes, use AskUserQuestion to confirm how to proceed.
Check for unstaged changes:
Changes not staged for commit)Untracked files)If unstaged changes exist:
{
"questions": [{
"question": "There are unstaged changes. How would you like to proceed?",
"header": "Unstaged",
"options": [
{"label": "Stage all", "description": "Run `git add .` to stage all changes"},
{"label": "Abort", "description": "Cancel the commit and handle changes manually"}
],
"multiSelect": false
}]
}
git add . then continue to Step 3Only proceed if all changes are properly staged:
Generate the commit message following the format, then use AskUserQuestion tool to confirm:
Proposed commit message:
<type>(<scope>): <subject>
<body if needed>
Co-Authored-By: Claude <noreply@anthropic.com>
Use AskUserQuestion tool with options:
Approve - Proceed to commitEdit message - User wants to modify the messageCancel - Abort the commitExample AskUserQuestion usage:
{
"questions": [{
"question": "Proceed with this commit message?",
"header": "Commit",
"options": [
{"label": "Approve", "description": "Create the commit with this message"},
{"label": "Edit message", "description": "Modify the commit message"},
{"label": "Cancel", "description": "Abort the commit"}
],
"multiSelect": false
}]
}
git commit -m "$(cat <<'EOF'
<type>(<scope>): <subject>
<body if needed>
Co-Authored-By: Claude <noreply@anthropic.com>
EOF
)"
git log -1 --oneline
feat: parse blocklet urls from dev output instead of constructing from did
feat: add blocklet-branch skill for branch management
feat: enhance blocklet-server-dev-setup skill with GitHub CLI authentication guidance
feat(agentloop): add verification skill (#1)
fix: gh move top
docs: prefer git URL format for marketplace installation
chore: initial commit
chore: cleanup hello world plugin
(#123)