菜单
Fix issues end-to-end — triage, diagnose, branch, fix, PR/MR, close. Supports GitHub (gh) and GitLab (glab) with cross-repo fixes and submodule bumps. USE WHEN fix issue, github issue, gitlab issue, bug report, fix bug, resolve issue, triage issue, gh issue, fix
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Pick brandable available domains via RDAP, detect broker listings, plan brand families, and choose registrars without overpaying premium tiers. USE WHEN picking a domain, naming a project, checking domain availability, registering a domain, brand research, TLD hack, ccTLD pricing.
Drive cmux from its Unix-socket CLI: open a new split, pane, or tab and run a command in it by sending text and keys, build declarative layouts, render a diff in the native viewer, and resolve window / workspace / pane / surface handles. USE WHEN opening tuicr or any command in a new cmux pane, splitting the current pane from the CLI, sending commands or keys to another surface, watching logs in a side pane, showing a diff in cmux, or scripting cmux layouts. For app config, persistence, and hooks see the cmux tldr.
Jujutsu (jj) as a colocated VCS front-end over git for AI-agent work: colocate strategy, git-hook-tool coexistence (Entire, gitleaks, safety-net), parallel agents via jj workspaces, op-log recovery, provisioning. USE WHEN colocating a repo with jj git init --colocate, deciding whether jj coexists with Entire / gitleaks / safety-net or other git-hook tooling, isolating parallel agents with jj workspace, recovering jj state with jj undo or op restore, or debugging jj-and-git interaction. For commit and push discipline see VersionControl's Jujutsu companion; for commands see the jj tldr.
Manage the pull request lifecycle: author the body to the house standard, create via gh or glab, retrieve and address feedback, retarget stacked PRs, merge and clean up. USE WHEN create a PR, open a pull request, draft a PR, write a PR body, PR description, address PR feedback, PR comments, retarget a stacked PR, PR merged but changes missing from main, merge a PR. For the merge-vs-PR-vs-discard decision use FinishBranch; for processing review feedback rigor use ReceiveReview; for authoring the review-request message use RequestReview.
Author a clear scoped request when asking for a code review. USE WHEN ready for review, finishing a task, or requesting review feedback on a piece of code. For creating the pull request itself use PullRequest.
Server-rendered web dashboards and apps in Rust using axum + htmx + Askama + rust-embed. USE WHEN building a web dashboard, adding a web UI to a CLI tool, server-rendered HTML, htmx partials, Askama templates, axum routes, embedded static assets, localhost webserver.
| name | FixIssue |
| version | 0.1.0 |
| description | Fix issues end-to-end — triage, diagnose, branch, fix, PR/MR, close. Supports GitHub (gh) and GitLab (glab) with cross-repo fixes and submodule bumps. USE WHEN fix issue, github issue, gitlab issue, bug report, fix bug, resolve issue, triage issue, gh issue, fix |
Fix an issue from triage to close. Platform-agnostic workflow with platform-specific CLI companions.
| Platform | CLI | Companion | Detect by |
|---|---|---|---|
| GitHub | gh | @GitHub.md | github.com in URL or gh origin |
| GitLab | glab | @GitLab.md | gitlab.com in URL or glab origin |
Auto-detect from the issue URL or remote origin. If ambiguous, ask the user.
| Format | Example |
|---|---|
owner/repo#N | N4M3Z/forge-council#8 |
| Issue URL (GitHub) | https://github.com/N4M3Z/forge-council/issues/8 |
| Issue URL (GitLab) | https://gitlab.com/group/project/-/issues/42 |
#N (current repo) | #8 |
When fixing issues in multi-repo or submodule projects, the fix often lives in a different repo than the issue.
| Symptom location | Typical fix location | Pattern |
|---|---|---|
| Consumer module | Shared library | Fix in lib, bump submodule in consumer |
| Module install/verify fails | Same module | Makefile, config, or stale submodule pointer |
| Skill broken across providers | Same module | SKILL.md content or SKILL.yaml metadata |
| Standalone plugin | Corresponding source module | Fix in source, then sync to standalone |
| Type | Branch name |
|---|---|
| Bug fix | fix/<slug> |
| Feature request | feat/<slug> |
| Documentation | docs/<slug> |
Slug: lowercase, hyphenated, derived from issue title. Keep under 50 characters.
Read the issue using the platform CLI. Extract:
See the platform companion for exact commands.
Before starting, check for open PRs/MRs that reference this issue and whether someone is assigned. If work exists, report to the user and ask whether to proceed, contribute, or stop.
Determine:
Use the Cross-Repo Topology table. For submodule-related failures, check the submodule pointer:
git -C REPO_PATH submodule status lib
Use the platform CLI to create a branch linked to the issue. See the platform companion for commands.
If the fix is cross-repo, create the branch in the fix repo, not the issue repo.
Fallback (any platform):
git checkout -b fix/<slug>
Read the relevant code. Identify the root cause. Implement the fix.
If cross-repo fix:
Testing checklist:
cargo test / make test / project-specific runnercargo clippy / make lintmake install && make verifyUse the platform CLI to create a PR (GitHub) or MR (GitLab) with:
fix:, feat:, docs:)See the platform companion for exact templates and auto-close keywords.
Submodule bump (after fix PR/MR merges in dependency):
git -C path/to/submodule checkout main && git -C path/to/submodule pull
git add path/to/submodule
git commit -m "chore: bump <submodule> for fix #N"
Same-repo: auto-closes via keywords in the PR/MR body.
Cross-repo: auto-close does NOT work. Manually close with a comment linking to the fix. See the platform companion for the close command.
Summarize:
Before posting any public-facing message via the platform CLI, use AskUserQuestion to show the draft message and get user approval. This applies to:
gh issue close -c, glab issue close -c)gh pr create --body, glab mr create --description)gh issue comment, glab issue note)Present the message as a preview option so the user can approve, edit, or reject it. Never post public messages without confirmation.
@ErrorResolver.md