Agent skill

Fix Issue

by r3bl-org in r3bl-org/r3bl-open-core

Guidelines for deeply exploring the problem space first and designing the best solution before implementing.

Apache-2.0Auto-check passedAgent Workflows

Install Fix Issue

skills CLI
$ npx skills add r3bl-org/r3bl-open-core --skill fix-issue -a claude-code

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

GitHub CLI
$ gh skill install r3bl-org/r3bl-open-core 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/r3bl-org/r3bl-open-core.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/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/

Facts

Skill name
fix-issue
GitHub stars
485
Token cost
~976 tokens
SKILL.md length
476 words
Files
1
Skills in repo
25
Repo updated
First seen
Licence
Apache-2.0

At a glance

Guidelines for deeply exploring the problem space first and designing the best solution before implementing.

  • Works in 5 steps: Deep Research (No Code Written) → Design Doc (Task File Creation) → User Review & Approval → …
  • Agent Workflows work in your project
  • SKILL.md covers When to Use and The Design-First Workflow
  • Calls gh

What it does

Fix Issue is an agent skill from r3bl-org/r3bl-open-core. Guidelines for deeply exploring the problem space first and designing the best solution before implementing.

Its SKILL.md is about 980 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 Agent Workflows. The repository describes itself as: TUI framework and developer productivity apps in Rust 🦀. The licence is Apache-2.0.

When your agent uses it

  • Agent Workflows work in your project

Example prompts

  • “Use the fix-issue skill to guideline for deeply exploring the problem space first and designing the best solution before implementing”
  • “/fix-issue”

Workflow steps

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

  1. Deep Research (No Code Written)
  2. Design Doc (Task File Creation)
  3. User Review & Approval
  4. Iterative Implementation
  5. Merge & Complete

What it can do on your machine

Read from SKILL.md and the folder at commit 89db352. 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:

    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    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 976 tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 476 words of instructions outside code blocks.

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

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 r3bl-org/r3bl-open-core at commit 89db352, republished under its Apache-2.0 licence (© r3bl-org). 476 words, ~976 tokens.

Download SKILL.mdSave it as .claude/skills/fix-issue/SKILL.md (or your agent's skills folder).
name
fix-issue
description
Guidelines for deeply exploring the problem space first and designing the best solution before implementing.

Issue Fix Workflow: Deep Exploration and Design

This skill codifies the "slow and steady" approach to solving non-trivial issues or adding features. It enforces exploring the problem space, considering alternative designs, and formalizing the design before writing any implementation code.

When to Use

Use this skill whenever you are:

  • Creating a new task file for a non-trivial issue or feature.
  • Asked by the user to "explore first", "design first", or "write a design doc".
  • Working on complex or architectural changes that span multiple components.

The Design-First Workflow

The workflow consists of four distinct steps:

┌───────────────────┐      ┌───────────────────┐      ┌───────────────────┐      ┌───────────────────┐
│ 1. Deep Research  │ ───► │  2. Design Doc    │ ───► │  3. User Review   │ ───► │ 4. Implementation │
│ (No Code Written) │      │  (Task MD File)   │      │   & Approval      │      │ (Iterative Step)  │
└───────────────────┘      └───────────────────┘      └───────────────────┘      └───────────────────┘
Step 1: Deep Research (No Code Written)

Before proposing any changes or writing a task file, gather context on the problem space:

  1. Read the issue description (e.g., via gh issue view <id>).
  2. Search the codebase to locate all relevant files, traits, types, and usages.
  3. Understand the control flow, thread boundaries, and lifecycle constraints.
  4. Do NOT write or modify any code during this step.
Step 2: Design Doc (Task File Creation)

Create the task file under task/issue-<id>-fix.md or task/<name>.md. Create a new git branch for this task, push it, and open a Draft PR using gh pr create --draft --fill to track the work.

Instead of a simple todo list, format this task file as a Design Document with the following sections:

1. Overview
  • Clear statement of the goal.
  • Context and reference to GitHub issues or PRs.
2. Problem Space & Constraints
  • Detailed analysis of the current code.
  • Specific limitations of the existing design.
  • Architectural and safety constraints (e.g., thread safety, locks, lifetimes, platform compatibility).
3. Design Alternatives

Present at least two (ideally three) alternative approaches. For each alternative, detail:

  • How it works: High-level explanation of the API and structural changes.
  • Pros: Benefits of this approach.
  • Cons: Drawbacks, complexity, or limitations.
  • Assessment: Feasibility, effort, and alignment with the project's design philosophy.
Show full SKILL.md (169 more words)Show less
4. Proposed Design
  • Which alternative was chosen and why.
  • Specific API signatures, type changes, and struct definitions.
  • Visual diagram (if applicable, using ASCII or Mermaid).
  • Threading, lock, and lifecycle impact analysis.
5. Implementation Plan

The very last section containing flat checklists grouped under phase headers.

  • Phase 1: Preparation / API Refactoring
  • Phase 2: Core Implementation
  • Phase 3: Integration & Testing
  • Every phase MUST end with a Mandatory manual review checkbox list for modified files.
Step 3: User Review & Approval

Present the newly created task file to the user.

  • Highlight the design alternatives and the proposed design.
  • Ask for feedback and wait for explicit approval before proceeding to implementation.
Step 4: Iterative Implementation

Only after the design doc is approved, load the task and begin implementation step-by-step.

  • Run quality checks (./check.fish) and pause for manual reviews frequently.
Step 5: Merge & Complete

Once the implementation is fully tested and manually reviewed:

  • Remind the user to run the /merge-pr slash command to push the final code and merge the existing Pull Request into main.

© r3bl-org, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/fix-issue of r3bl-org/r3bl-open-core.

Open the folder on GitHubat commit 89db352

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
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Fix Issue this skillr3bl-org/r3bl-open-core485—~976Automated safety check: PassApache-2.0
Orca CLIstablyai/orca87k2 repos~593Automated safety check: PassMIT
OpenSpec Guided OnboardingFission-AI/OpenSpec71k1 repos~4.5kAutomated safety check: PassMIT
Claude Code Plugin Structureanthropics/claude-plugins-official38k10 repos~3.4kAutomated safety check: PassApache-2.0
Neat-Freak Knowledge CloseoutKKKKhazix/khazix-skills21k—~1.9kAutomated safety check: PassMIT
O2 Review Loopopenobserve/openobserve22k—~3.7kAutomated safety check: PassAGPL-3.0

Similar skills

  • Orca CLI

    stablyai/orca

    Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…

    87k GitHub starsUsed in 2 repos~593 tokens
    Agent WorkflowsAuto-check passed
  • OpenSpec Guided Onboarding

    Fission-AI/OpenSpec

    Walks you through a complete OpenSpec workflow cycle with narration while doing real work in your codebase.

    71k GitHub starsUsed in 1 repo~4.5k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Plugin Structure

    anthropics/claude-plugins-official

    Official

    Explains the directory layout, plugin.json manifest and component organization of a Claude Code plugin, including auto-discovery and portable paths.

    38k GitHub starsUsed in 10 repos~3.4k tokens
    Agent WorkflowsAuto-check passed
  • Neat-Freak Knowledge Closeout

    KKKKhazix/khazix-skills

    Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.

    21k GitHub stars~1.9k tokensUpdated 7 days ago
    Agent WorkflowsAuto-check passed
  • O2 Review Loop

    openobserve/openobserve

    Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.

    22k GitHub stars~3.7k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Autoresearch Iteration Loop

    uditgoenka/autoresearch

    Runs an autonomous modify, verify, keep-or-discard loop against any metric, with subcommands for planning, debugging, fixing, security audits, shipping and more.

    6.5k GitHub starsUsed in 1 repo~2k tokens
    Agent WorkflowsAuto-check passed

More from r3bl-org/r3bl-open-core

All 25 skills in this repo
  • Analyze Log Files

    r3bl-org/r3bl-open-core

    Analyze log files by stripping ANSI escape sequences first. An agent skill from r3bl-org/r3bl-open-core.

    485 GitHub stars~632 tokensUpdated today
    Auto-check: notes
  • Analyze Performance

    r3bl-org/r3bl-open-core

    Establish performance baselines and detect regressions using flamegraph analysis.

    485 GitHub stars~2k tokensUpdated today
    Auto-check passed
  • Check Bounds Safety

    r3bl-org/r3bl-open-core

    Apply type-safe bounds checking patterns using VPIndex/VPLength types instead of usize.

    485 GitHub stars~4.1k tokensUpdated today
    Auto-check passed
  • Release Crate

    r3bl-org/r3bl-open-core

    Publish a crate release to crates.io with changelog, standalone release notes, git tag, and GitHub release.

    485 GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Organize Modules

    r3bl-org/r3bl-open-core

    Apply private modules with public re-exports (barrel export) pattern for clean API design.

    485 GitHub stars~5.8k tokensUpdated today
    Auto-check passed
  • Check Code Quality

    r3bl-org/r3bl-open-core

    Run comprehensive Rust code quality checks including compilation, linting, documentation, and tests.

    485 GitHub stars~3.8k tokensUpdated today
    Auto-check passed

Questions about Fix Issue

What does Fix Issue do?

Guidelines for deeply exploring the problem space first and designing the best solution before implementing. Fix Issue is an agent skill from r3bl-org/r3bl-open-core. Guidelines for deeply exploring the problem space first and designing the best solution before implementing.

When should I use Fix Issue?

Fix Issue fits situations like: agent Workflows work in your project.

How do I install Fix Issue in Claude Code?

Run `npx skills add r3bl-org/r3bl-open-core --skill fix-issue -a claude-code`. Or copy the skill folder (.agents/skills/fix-issue in r3bl-org/r3bl-open-core) 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 r3bl-org/r3bl-open-core --skill fix-issue -a codex`. Or copy the skill folder (.agents/skills/fix-issue in r3bl-org/r3bl-open-core) 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 r3bl-org/r3bl-open-core --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 (gh).

Does Fix Issue access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. 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 976 tokens (SKILL.md is roughly 3.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: Orca CLI (stablyai/orca, 87k stars), OpenSpec Guided Onboarding (Fission-AI/OpenSpec, 71k stars), Claude Code Plugin Structure (anthropics/claude-plugins-official, 38k stars) and Neat-Freak Knowledge Closeout (KKKKhazix/khazix-skills, 21k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fix Issue?

r3bl-org (a GitHub organization) maintains it in r3bl-org/r3bl-open-core, which has 485 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on October 8, 2026.

Source: r3bl-org/r3bl-open-core on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.