Fix Issue

Community

poshan0126

fix-issue

Take a GitHub issue from number to tested fix — read the issue and comments, reproduce, locate the cause, fix with a regression test, and prep a PR that closes it.

Overview

Publisher	poshan0126
Repository	`dotclaude`
Skill name	`fix-issue`
Stars	870
Forks	204
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by poshan0126 on GitHub. Read the source before you install it.

Installation

Install the Fix Issue AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/poshan0126/dotclaude/tree/main/skills/fix-issue
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/poshan0126/dotclaude.git /tmp/dotclaude
mkdir -p .claude/skills
cp -r /tmp/dotclaude/skills/fix-issue .claude/skills/fix-issue

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Fix Issue in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Fix Issue on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Fix Issue is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Work a GitHub issue end to end. $ARGUMENTS is the issue number or URL; if omitted, run gh issue list --assignee @me --state open and ask which one.

Step 1: Understand the issue

The live issue thread (or your open assigned issues, when no number was given) is injected below — no need to fetch it again:

!gh issue view $ARGUMENTS --comments 2>/dev/null || gh issue list --assignee @me --state open 2>/dev/null || echo "(no issue arg — paste the issue details)"

The thread above is the real spec — read the body AND the discussion; the decision that changes the fix is often in comment 7.
Extract: expected behavior, actual behavior, reproduction steps, acceptance criteria, and any decisions already made in the thread.
If the issue is ambiguous on something that changes the fix (which behavior is correct? which platform?), ask the user — do NOT guess and do NOT ask in the issue thread without being told to.

Step 2: Classify and branch

Bug → follow /debug-fix discipline: reproduce it first (failing test or manual repro), then investigate. No fix before reproduction.
Small feature / chore → follow /tdd discipline if a test runner exists: failing test, minimum code, refactor.
Propose a branch named fix/issue-$NUMBER-<slug> (or feat/...), matching any existing convention visible in git branch -a. Confirm before creating.

Step 3: Locate and fix

Find the code path from the symptoms: grep for the error message, the feature's entry point, or names from the issue.
Make the smallest change that satisfies the acceptance criteria. Resist adjacent refactoring — note it for a follow-up instead.
Every bug fix ships with a regression test that fails on the old code. If you can't write one, say why in the PR body.

Step 4: Verify against the issue

Re-run the reproduction from Step 1 — confirm the reported behavior is gone.
Run the tests for the touched area, then lint/typecheck.
Walk the acceptance criteria one by one; quote each with its status.

Step 5: Ship it

Hand off to /ship (or follow its discipline): commit message and PR body must include Fixes #$NUMBER so the merge auto-closes the issue.
PR body: one-line cause, one-line fix, the regression test, and anything from the issue thread that influenced the approach.
After the PR exists, offer to comment the PR link on the issue (gh issue comment — requires confirmation; it's outward-facing).

Rules

Never start coding before Step 1 is complete — the thread often contains a decision that invalidates the obvious fix.
One issue per branch per PR. If the issue is really three issues, say so and fix the one that was asked.
If reproduction is impossible (can't access the environment, missing credentials), report exactly what's missing instead of fixing blind.

Frequently asked questions

What does the Fix Issue AI skill do?

Take a GitHub issue from number to tested fix — read the issue and comments, reproduce, locate the cause, fix with a regression test, and prep a PR that closes it.

Why use Fix Issue on TypingMind?

Because you install it once and use it with any model. Fix Issue is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Fix Issue in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/poshan0126/dotclaude/tree/main/skills/fix-issue. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Fix Issue?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Fix Issue?

As many as you like. As long as a model supports skills, you can use Fix Issue with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Fix Issue AI skill free?

Yes. It is published on GitHub by poshan0126 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Gitcrawl

openclaw

OrganizationPopular

GitHub archive: issue/PR search, sync freshness, duplicate clusters, current GitHub handoff, and Gitcrawl repo work.

Graincrawl

Granola archive: search, sync freshness, notes, transcripts, panels, SQL counts, and Graincrawl repo work.

Openclaw Changelog Update

openclaw

OrganizationPopular

Regenerate OpenClaw release changelog sections from git history before beta, stable, or extended-stable releases.

Openclaw Ci Limits

Manage OpenClaw GitHub Actions and Blacksmith CI capacity, runner-registration budgets, fanout caps, main-push single-flight, shard sizing, hosted-runner offload, queue health, and safe…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Step 1: Understand the issue

Step 2: Classify and branch

Step 3: Locate and fix

Step 4: Verify against the issue

Step 5: Ship it

Rules

Frequently asked questions

Related AI Skills

Set up your own AI workspace now