New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Fix

by kdlbs in kdlbs/kandev

Diagnose a Kandev bug, reconcile its requirements and system design, create a reviewable fix plan and work orders, then hand off for explicit TDD implementation.

AGPL-3.0Auto-check passedTesting & QA

Install Fix

skills CLI
$ npx skills add kdlbs/kandev --skill fix -a claude-code

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

GitHub CLI
$ gh skill install kdlbs/kandev fix --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/kdlbs/kandev.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/fix .claude/skills/fix && 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
GitHub stars
909
Token cost
~1.5k tokens
SKILL.md length
798 words
Files
1
Skills in repo
45
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Diagnose a Kandev bug, reconcile its requirements and system design, create a reviewable fix plan and work orders, then hand off for explicit TDD implementation.

  • Works in 6 steps: Evidence and root cause → Reconcile specifications → Create the fix package → …
  • Tasks that involve Test-driven development
  • SKILL.md covers Core flow, Phase 0: Evidence and root cause, Phase 1: Reconcile… and Phase 2: Create the fix package, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Fix is an agent skill from kdlbs/kandev. Diagnose a Kandev bug, reconcile its requirements and system design, create a reviewable fix plan and work orders, then hand off for explicit TDD implementation.

Its SKILL.md is about 1.5k 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 Testing & QA, covering Test-driven development. The repository describes itself as: AI Kanban & Development Environment. Orchestrate multiple agents, review changes, open PRs. Multi-provider, self-hostable, no telemetry. The licence is AGPL-3.0.

When your agent uses it

  • Tasks that involve Test-driven development

Example prompts

  • “/fix”

Requirements

  • Python 3

Workflow steps

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

  1. Evidence and root cause
  2. Reconcile specifications
  3. Create the fix package
  4. Design-package handoff
  5. Implement with TDD
  6. PR review

What it can do on your machine

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

    No scripts in the folder and no shell commands in SKILL.md.

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

  • Network

    No URLs in SKILL.md.

    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 loads about 1.5k tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 798 words of instructions outside code blocks.

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

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 kdlbs/kandev at commit b734113, republished under its AGPL-3.0 licence (© kdlbs). 798 words, ~1,486 tokens.

Download SKILL.mdSave it as .claude/skills/fix/SKILL.md (or your agent's skills folder).
name
fix
description
Diagnose a Kandev bug, reconcile its requirements and system design, create a reviewable fix plan and work orders, then hand off for explicit TDD implementation.

Fix

Use the same durable workflow as feature work. Diagnose the defect first. Then reconcile specifications and create the fix plan and work orders before you change production code.

Core flow

text
Evidence -> Root cause -> Requirement conformance -> System-design check -> Fix plan + work orders -> Handoff -> Explicit implementation request -> TDD -> PR review

Do not patch production code before the planning checkpoint unless the user explicitly opts out.

Phase 0: Evidence and root cause

When a bug comes from an issue tracker, read the canonical issue and each image attachment. Reproduce the behavior with existing tests, a read-only trace, or a minimal temporary reproduction.

State:

  • The incorrect behavior and its conditions.
  • The root cause.
  • The smallest reliable reproduction.
  • The intended regression-test level and path.

If the cause remains uncertain, stop and ask the user.

Phase 1: Reconcile specifications

Run the /interview-me assumption check for intended behavior and repair scope. Reuse active acceptance criteria for clear regressions. Ask only about material choices that evidence and prior instructions do not settle.

Read docs/specs/README.md, the owning system index, and the relevant requirement and system-design documents. Use the legacy catalog only when the system has not migrated. Read the owning system README.md and use this command for discovery:

python3 scripts/list-docs.py specs --format paths

Add --kind legacy when the system has not migrated.

Search adjacent systems before you create or move an artifact. A UI symptom does not make the repair UI-owned. Update the system that owns the failed contract, and include observable UI recovery there when applicable.

Classify the bug:

  1. Implementation violates an active acceptance criterion. Reference the existing AC-* ID. Do not create or rewrite a requirement.
  2. The intended behavior is missing from requirements. Add the smallest requirement and acceptance criteria that define it.
  3. The intended product behavior changes. Amend or supersede the affected requirement. Record the compatibility effect.
  4. The technical design is wrong or incomplete. Update the system design. Keep observable behavior in requirements.

Do not create a standalone repair specification. The requirement is the durable behavioral source. The plan and work orders record this repair.

For predicates over collections or inventory, state the quantifier explicitly: distinguish existential conditions such as “at least one live row” from universal conditions such as “all rows.” When behavior depends on that distinction, require a mixed-state regression containing both live and failed or deleted rows.

Do not create parallel feature and UI requirements for one repair. A separate UI requirement is valid only when the repair changes an independent reusable UI contract.

Use /record when the correction establishes a durable boundary, ownership rule, public contract, persistence rule, or security invariant with meaningful alternatives.

Phase 2: Create the fix package

Create docs/plans/<fix-slug>/plan.md and sibling work orders through /plan.

The package must:

  • Reference the affected REQ-* and AC-* IDs.
  • Reference the applicable system design.
  • State the confirmed root cause.
  • Name the regression test that fails before the correction.
  • Name exact files, dependencies, acceptance conditions, and commands.
  • Use dependency waves only when they clarify implementation order.
  • For rendered UI changes, include ASCII previews in the plan and relevant UI work orders per docs/specs/guide/plans-and-work-orders.md#ascii-ui-previews. Show before/after when it explains the defect and correction.

Keep work orders sequential by default. A wave does not authorize delegation.

Show full SKILL.md (281 more words)Show less

Phase 3: Design-package handoff

Before you change production or permanent test code, report:

  • Root cause and reproduction evidence.
  • Requirement IDs and system-design paths.
  • Plan and work-order paths.
  • Dependency order and exact commands.
  • Risks and exclusions.
  • For UI changes, a compact inline ASCII preview of the correction, including phone composition when different, and links to the full plan/work-order views.

Then end the turn. Do not ask the user to approve the package or switch models. Wait for a later explicit implementation request.

Phase 4: Implement with TDD

After the explicit request:

  1. Change the work order to in_progress.
  2. Write and run the regression test.
  3. Make sure that the test fails for the expected reason.
  4. Implement the minimum correction.
  5. Run the work order's exact commands.
  6. Change the work order to done and synchronize plan.md.

For persisted defaults or coupled settings, inspect every write and reset path. Cover explicit empty and null values when they affect the contract.

If the user authorizes subagents, obey /planner-orchestration. Use native delegation, compact work-order context, no recursive delegation, and no full-history fork.

Phase 5: PR review

After all work-order checks pass, commit, push, and open the PR. Do not add an automatic local simplify, QA, broad review, security review, or verification pass.

Use /pr-fixup only for a CI error or an actionable reviewer finding. Run the affected work-order check after a correction.

Stop conditions

Stop when the root cause is uncertain, specifications and code disagree, the repair needs a new material design, or the same targeted check fails three times.

Final report

Report the root cause, requirement IDs, system-design path, plan and work-order paths, changed files, commands, results, authorized subagents, and PR status.

© kdlbs, AGPL-3.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 of kdlbs/kandev.

Open the folder on GitHubat commit b734113

Compare with similar skills

Fix 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 compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Fix this skillkdlbs/kandev909—~1.5kAutomated safety check: PassAGPL-3.0
Rust TDD Workflowrtk-ai/rtk83k—~753Automated safety check: NotesApache-2.0
RTK Filter TDD in Rustrtk-ai/rtk83k—~1.9kAutomated safety check: NotesApache-2.0
Test Guidelinesgetsentry/sentry-dart873—~3.1kAutomated safety check: PassMIT
Evidence-First Development LoopAmazingAng/old-coder749—~5.4kAutomated safety check: NotesMIT
Gh IssuesTypedDevs/bashunit4341 repos~1.7kAutomated safety check: NotesMIT

Similar skills

  • Rust TDD Workflow

    rtk-ai/rtk

    Enforces red-green-refactor for Rust work, with idiomatic test patterns, a naming convention and a pre-commit gate of cargo fmt, clippy and test.

    83k GitHub stars~753 tokensUpdated yesterday
    Testing & QAAuto-check: notes

  • RTK Filter TDD in Rust

    rtk-ai/rtk

    Enforces red-green-refactor for new RTK output filters in Rust, using real captured fixtures, snapshot tests with insta and token-savings assertions.

    83k GitHub stars~1.9k tokensUpdated yesterday
    Testing & QAAuto-check: notes

  • Test Guidelines

    getsentry/sentry-dart

    Official

    Enforce Sentry Dart/Flutter SDK test conventions for naming, structure, and fixtures.

    873 GitHub stars~3.1k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Evidence-First Development Loop

    AmazingAng/old-coder

    Replaces line-by-line code review with an approved executable spec and a gauntlet of tests, types, coverage, and mutation checks the code must survive.

    749 GitHub stars~5.4k tokensUpdated 1 mo ago
    Testing & QAAuto-check: notes

  • Gh Issues

    TypedDevs/bashunit

    Walk over all open GitHub issues that are unassigned or assigned to the current user, and process each one via the /gh-issue skill, sequentially.

    434 GitHub starsUsed in 1 repo~1.7k tokens
    Testing & QAAuto-check: notes

  • Agent Harness Testing Methodology

    huiliyi37/Tianshu-harness

    Guides an agent through probing an unfamiliar project's test setup, then choosing a red-light-first testing strategy matched to the task type.

    1.1k GitHub stars~1k tokensUpdated today
    Testing & QAAuto-check: notes

More from kdlbs/kandev

All 45 skills in this repo

  • PR Walkthrough

    kdlbs/kandev

    Generate a single-file HTML walkthrough that explains a PR's purpose, user impact, interface changes, compatibility risks, and implementation.

    909 GitHub stars~6.2k tokensUpdated today
    Auto-check passed

  • Debug

    kdlbs/kandev

    Diagnose Kandev bugs, running-instance issues, UI/browser failures, and runtime behavior.

    909 GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Harness Improvement

    kdlbs/kandev

    Improve Kandev's AI harness from session learnings or explicit requests.

    909 GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Diagram Design

    kdlbs/kandev

    Create branded architecture, IT current-state, flowchart, sequence, state machine, ER/data model, timeline, swimlane, quadrant, radar/spider, polar chart (polar/radial lollipop), loop/flywheel…

    909 GitHub starsUsed in 1 repo~8k tokens
    Auto-check passed

  • TDD

    kdlbs/kandev

    Implement changes using Test-Driven Development (Red-Green-Refactor).

    909 GitHub stars~4.2k tokensUpdated today
    Auto-check passed

  • Verify

    kdlbs/kandev

    Run a broad local verification audit only when the user explicitly requests it or PR/CI remediation requires it.

    909 GitHub stars~2.7k tokensUpdated today
    Auto-check passed

Categories

Questions about Fix

What does Fix do?

Diagnose a Kandev bug, reconcile its requirements and system design, create a reviewable fix plan and work orders, then hand off for explicit TDD implementation. Fix is an agent skill from kdlbs/kandev. Diagnose a Kandev bug, reconcile its requirements and system design, create a reviewable fix plan and work orders, then hand off for explicit TDD implementation.

When should I use Fix?

Fix fits situations like: tasks that involve Test-driven development.

How do I install Fix in Claude Code?

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

How do I install Fix in Codex?

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

Can I use Fix 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 kdlbs/kandev --skill fix -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, .gemini/skills/fix, .github/skills/fix and .opencode/skills/fix in your project.

What does Fix need to run?

SKILL.md names no scripts, command-line tools or credentials: Fix is instructions for the agent only. Our summary lists: Python 3.

Does Fix access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Fix 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 use?

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

How many tokens does Fix use?

About 1.5k tokens (SKILL.md is roughly 5.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?

Skills that share tags, products or a category with Fix: Rust TDD Workflow (rtk-ai/rtk, 83k stars), RTK Filter TDD in Rust (rtk-ai/rtk, 83k stars), Test Guidelines (getsentry/sentry-dart, 873 stars) and Evidence-First Development Loop (AmazingAng/old-coder, 749 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fix?

kdlbs (a GitHub organization) maintains it in kdlbs/kandev, which has 909 GitHub stars. The repository holds 45 skills in this directory. The repository was last updated on October 8, 2026.

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