Agent skill

Fix Issue

Fix a GitHub issue using git worktree for isolation. An agent skill from nex-agi/NexRL.

Apache-2.0Auto-check passedDevelopment

Install Fix Issue

skills CLI

$ npx skills add nex-agi/NexRL --skill fix-issue -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install nex-agi/NexRL fix-issue --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/nex-agi/NexRL.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/fix-issue .claude/skills/fix-issue && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "fix-issue" agent skill from https://github.com/nex-agi/NexRL/tree/main/.claude/skills/fix-issue into .claude/skills/fix-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-issue", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/nex-agi/NexRL/tree/main/.claude/skills/fix-issue

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add nex-agi/NexRL --skill fix-issue -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install nex-agi/NexRL fix-issue --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nex-agi/NexRL.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/fix-issue .agents/skills/fix-issue && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "fix-issue" agent skill from https://github.com/nex-agi/NexRL/tree/main/.claude/skills/fix-issue into .agents/skills/fix-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-issue", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add nex-agi/NexRL --skill fix-issue -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install nex-agi/NexRL fix-issue --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nex-agi/NexRL.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/fix-issue .cursor/skills/fix-issue && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "fix-issue" agent skill from https://github.com/nex-agi/NexRL/tree/main/.claude/skills/fix-issue into .cursor/skills/fix-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-issue", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/nex-agi/NexRL.git --path .claude/skills/fix-issue

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add nex-agi/NexRL --skill fix-issue -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install nex-agi/NexRL fix-issue --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nex-agi/NexRL.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/fix-issue .gemini/skills/fix-issue && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "fix-issue" agent skill from https://github.com/nex-agi/NexRL/tree/main/.claude/skills/fix-issue into .gemini/skills/fix-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-issue", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install nex-agi/NexRL fix-issue

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add nex-agi/NexRL --skill fix-issue -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/nex-agi/NexRL.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/fix-issue .github/skills/fix-issue && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "fix-issue" agent skill from https://github.com/nex-agi/NexRL/tree/main/.claude/skills/fix-issue into .github/skills/fix-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-issue", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add nex-agi/NexRL --skill fix-issue -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install nex-agi/NexRL fix-issue --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nex-agi/NexRL.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/fix-issue .opencode/skills/fix-issue && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "fix-issue" agent skill from https://github.com/nex-agi/NexRL/tree/main/.claude/skills/fix-issue into .opencode/skills/fix-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-issue", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: fix-issue
GitHub stars: 119
Token cost: ~733 tokens
SKILL.md length: 156 words
Files: 1
Skills in repo: 6
Repo updated: Sep 17, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Fix a GitHub issue using git worktree for isolation. An agent skill from nex-agi/NexRL.

Works in 11 steps: Verify Prerequisites → Fetch Issue → Update Issue Status → …
Tasks that involve Git worktrees
Calls git, gh and python; reaches github.com

What it does

Fix Issue is an agent skill from nex-agi/NexRL. Fix a GitHub issue using git worktree for isolation. Fetches issue, creates worktree, implements fix, then creates PR.

Its SKILL.md is about 730 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Git worktrees. It works with GitHub and Git. The repository describes itself as: NexRL is an ultra-loosely-coupled LLM post-training framework. The licence is Apache-2.0.

When your agent uses it

Tasks that involve Git worktrees

Example prompts

“/fix-issue”

Requirements

Python 3

Workflow steps

11 steps, taken from the step headings in SKILL.md.

Verify Prerequisites
Fetch Issue
Update Issue Status
Create Worktree
Read Documentation First
Plan the Fix
Implement
Test
Commit and PR
Handle Blockers
Cleanup (after PR merged)

What it can do on your machine

Read from SKILL.md and the folder at commit 53dcdec. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- git
- gh
- python
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Fix Issue loads about 733 tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 156 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~32
When it runs · the whole SKILL.md, loaded when a task matches: ~733

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from nex-agi/NexRL at commit 53dcdec, republished under its Apache-2.0 licence (© nex-agi). 156 words, ~733 tokens.

Download SKILL.mdSave it as .claude/skills/fix-issue/SKILL.md (or your agent's skills folder).

name: fix-issue
description: Fix a GitHub issue using git worktree for isolation. Fetches issue, creates worktree, implements fix, then creates PR.

Fix Issue Workflow (Worktree-Based)

Workflow

Step 1: Verify Prerequisites

bash

gh auth status

Step 2: Fetch Issue

bash

ISSUE_NUM=<number>
gh issue view $ISSUE_NUM --repo "${REPO_OWNER}/${REPO_NAME}" --json number,title,body,state,labels

If closed, confirm with user before proceeding.

Step 3: Update Issue Status

bash

gh issue comment $ISSUE_NUM --repo china-qijizhifeng/NexRL \
  --body "🤖 Agent picking up this issue. Creating worktree branch \`agent/issue-${ISSUE_NUM}\`."

gh issue edit $ISSUE_NUM --repo china-qijizhifeng/NexRL \
  --add-label "status:in-progress" 2>/dev/null || true

Fetch Shared Knowledge

Clone or update the shared knowledge repo for common scripts and docs.

bash

REPO_ROOT=$(git rev-parse --show-toplevel)
SHARED_KNOWLEDGE="${REPO_ROOT}/../nex-taas-shared-knowledge"
if [ ! -d "$SHARED_KNOWLEDGE" ]; then
  git clone https://github.com/china-qijizhifeng/nex-taas-shared-knowledge.git "$SHARED_KNOWLEDGE"
else
  git -C "$SHARED_KNOWLEDGE" pull --ff-only 2>/dev/null || true
fi

Step 4: Create Worktree

bash

REPO_ROOT=$(git rev-parse --show-toplevel)
cd "$REPO_ROOT"
git fetch origin

BRANCH="agent/issue-${ISSUE_NUM}"
WORKTREE_DIR="${REPO_ROOT}/../worktrees/NexRL-issue-${ISSUE_NUM}"

git worktree add "$WORKTREE_DIR" -b "$BRANCH" "origin/main"
cd "$WORKTREE_DIR"

Step 5: Read Documentation First

Before coding, read relevant docs per .ai-instructions/developing/documentation.md:

docs/developer-guide/ for architecture understanding
Component-specific docs for the area being changed

Step 6: Plan the Fix

Enter plan mode. Consider:

Root cause analysis (for bugs)
Files that need changes
Impact on other components
Documentation updates needed

Step 7: Implement

Work in the worktree directory. Follow:

.ai-instructions/developing/ conventions
Run python -m black and python -m isort on changed files
Ensure license headers present

Step 8: Test

Run project tests (use testing skill):

bash

python -m pytest tests/ -v
python -m pylint nexrl/ --rcfile=.pylintrc -rn -sn

Step 9: Commit and PR

Use git-commit skill, then github-pr skill. PR body should include: Fixes #ISSUE_NUM

Step 10: Handle Blockers

If blocked:

bash

gh issue edit $ISSUE_NUM --repo china-qijizhifeng/NexRL \
  --remove-label "status:in-progress" --add-label "status:blocked"

gh issue comment $ISSUE_NUM --repo china-qijizhifeng/NexRL --body "
🚧 Blocked: <describe the problem>
Need guidance on: <specific question>
Progress so far: <what's been done>"

Step 11: Cleanup (after PR merged)

bash

REPO_ROOT=$(git rev-parse --show-toplevel)
cd "$REPO_ROOT"
git worktree remove "$WORKTREE_DIR"
git branch -D "$BRANCH"

Files

Just SKILL.md in .claude/skills/fix-issue of nex-agi/NexRL.

Open the folder on GitHubat commit 53dcdec

Compare with similar skills

Fix Issue next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Fix Issue compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Fix Issue this skillnex-agi/NexRL	119	—	~733	Automated safety check: Pass	Apache-2.0	21 days ago
Git Worktree Runnerdyoshikawa/rulesync	1.5k	—	~1.3k	Automated safety check: Notes	MIT	today
Branch Standup Facilitatorthedotmack/claude-mem	98k	—	~1.7k	Automated safety check: Notes	Apache-2.0	yesterday
Project Session ManagerYeachan-Heo/oh-my-claudecode	40k	—	~4k	Automated safety check: Pass	MIT	today
Pre-Release PR Triagejamiepine/voicebox	57k	—	~3.1k	Automated safety check: Pass	MIT	yesterday
Ff Worktreesdamus-io/damus	2.1k	—	~451	Automated safety check: Pass	GPL-3.0	26 days ago

Similar skills

Git Worktree Runner
dyoshikawa/rulesync
Manages git worktrees using git-worktree-runner (gtr). An agent skill from dyoshikawa/rulesync.
1.5k GitHub stars~1.3k tokensUpdated today
DevelopmentAuto-check: notes
Branch Standup Facilitator
thedotmack/claude-mem
Facilitates a read-only standup between git worktrees, branches or PRs, where each acts as an agent in a shared markdown chat to agree one consolidation plan.
98k GitHub stars~1.7k tokensUpdated yesterday
DevelopmentAuto-check: notes
Project Session Manager
Yeachan-Heo/oh-my-claudecode
Creates isolated git worktrees, with optional tmux sessions, for PR reviews, issue fixes and feature work across projects and repositories.
40k GitHub stars~4k tokensUpdated today
DevelopmentAuto-check passed
Pre-Release PR Triage
jamiepine/voicebox
Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.
57k GitHub stars~3.1k tokensUpdated yesterday
DevelopmentAuto-check passed
Ff Worktrees
damus-io/damus
Fast-forward master and every git worktree branch up to a target ref (default github/master), skipping any worktree with unmerged commits.
2.1k GitHub stars~451 tokensUpdated 26 days ago
DevelopmentAuto-check passed
Clean Complete Branches
jtenniswood/espcontrol
Clean up completed Git branches and worktrees for this repository both locally and on GitHub.
1.1k GitHub stars~820 tokensUpdated today
DevelopmentAuto-check passed

Questions about Fix Issue

What does Fix Issue do?

Fix a GitHub issue using git worktree for isolation. An agent skill from nex-agi/NexRL. Fix Issue is an agent skill from nex-agi/NexRL. Fix a GitHub issue using git worktree for isolation.

When should I use Fix Issue?

Fix Issue fits situations like: tasks that involve Git worktrees.

How do I install Fix Issue in Claude Code?

Run `npx skills add nex-agi/NexRL --skill fix-issue -a claude-code`. Or copy the skill folder (.claude/skills/fix-issue in nex-agi/NexRL) into .claude/skills/fix-issue in your project. Claude Code loads it when a task matches its description.

How do I install Fix Issue in Codex?

Run `npx skills add nex-agi/NexRL --skill fix-issue -a codex`. Or copy the skill folder (.claude/skills/fix-issue in nex-agi/NexRL) into .agents/skills/fix-issue in your project. Codex loads it when a task matches its description.

Can I use Fix Issue in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nex-agi/NexRL --skill fix-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fix-issue, .gemini/skills/fix-issue, .github/skills/fix-issue and .opencode/skills/fix-issue in your project.

What does Fix Issue need to run?

Going by SKILL.md and its folder, Fix Issue needs the command-line tools its instructions call (git, gh and python). Our summary lists: Python 3.

Does Fix Issue access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Fix Issue safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Fix Issue use?

Fix Issue is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Fix Issue use?

About 733 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Fix Issue?

Skills that share tags, products or a category with Fix Issue: Git Worktree Runner (dyoshikawa/rulesync, 1.5k stars), Branch Standup Facilitator (thedotmack/claude-mem, 98k stars), Project Session Manager (Yeachan-Heo/oh-my-claudecode, 40k stars) and Pre-Release PR Triage (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fix Issue?

nex-agi (a GitHub organization) maintains it in nex-agi/NexRL, which has 119 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on September 17, 2026.

Source: nex-agi/NexRL on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Fix Issue

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Fix Issue Workflow (Worktree-Based)

Workflow

Step 1: Verify Prerequisites

Step 2: Fetch Issue

Step 3: Update Issue Status

Fetch Shared Knowledge

Step 4: Create Worktree

Step 5: Read Documentation First

Step 6: Plan the Fix

Step 7: Implement

Step 8: Test

Step 9: Commit and PR

Step 10: Handle Blockers

Step 11: Cleanup (after PR merged)

Files

Compare with similar skills

Similar skills

More from nex-agi/NexRL

Related

Questions about Fix Issue