A workflow for investigating and fixing software problems, including bugs, failed tests, build and deployment issues, type errors, lint errors, log errors, and interface issues.

Use it whenever code, tests, continuous integration, types, linting, logs, or a user interface is not working as expected.

It provides a repeatable path from finding the cause to checking the fix, including optional human review and parallel investigation.

ck:fix — Skill for Claude Code by manhvann/codexkit

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add manhvann/codexkit --skill fix

Clone the repo

git clone --depth 1 https://github.com/manhvann/codexkit

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/manhvann/codexkit/fix/github.svg)](https://agentmods.dev/skills/manhvann/codexkit/fix)

Your own site

<a href="https://agentmods.dev/skills/manhvann/codexkit/fix"><img src="https://agentmods.dev/badge/skills/manhvann/codexkit/fix/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/manhvann/codexkit/fix"><img src="https://agentmods.dev/badge/skills/manhvann/codexkit/fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,143 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

medium Excessive Agency · line 27
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00037	$0.01143
Opus 5.5	$0.00015	$0.00457
Sonnet 5.5	$0.00007	$0.00229
Haiku 4.5	$0.00004	$0.00114

Measured 1mo ago against content hash 34ba9607eb34, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ck:fix scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/fix/SKILL.md · 112 lines

How it starts

The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Fixing

Unified skill for fixing issues of any complexity with intelligent routing.

Arguments

--auto - Activate autonomous mode (default)
--review - Activate human-in-the-loop review mode
--quick - Activate quick mode
--parallel - Activate parallel mode: route to parallel fullstack_developer agents per issue

Workflow

Step 1: Mode Selection

First action: If there is no "auto" keyword in the request, ask the user to determine workflow mode:

Option	Recommend When	Behavior
Autonomous (default)	Simple/moderate issues	Auto-approve if score >= 9.5 & 0 critical
Human-in-the-loop Review	Critical/production code	Pause for approval at each step
Quick	Type errors, lint, trivial bugs	Fast debug → fix → review cycle

See references/mode-selection.md for the mode-selection prompt format.

Step 2: Debug

Activate ck:debug skill.
Guess all possible root causes.
Prefer multiple Explore/scout agents in parallel to verify each hypothesis when the runtime exposes delegation; otherwise use parallel searches and report the limitation.
Create report with all findings for the next step.

Step 3: Complexity Assessment & Task Orchestration

Classify before routing. See references/complexity-assessment.md.

Level	Indicators	Workflow
Simple	Single file, clear error, type/lint	`references/workflow-quick.md`
Moderate	Multi-file, root cause unclear	`references/workflow-standard.md`
Complex	System-wide, architecture impact	`references/workflow-deep.md`
Parallel	2+ independent issues OR `--parallel` flag	Parallel `fullstack_developer` agents

Task Orchestration (Moderate+ only): After classifying, use available task-tracking tools for all phases upfront with dependencies. See references/task-orchestration.md.

Skip for Quick workflow (< 3 steps, overhead exceeds benefit)
Create tracked tasks with dependency chains when task tools exist
Update task/checklist state as each phase completes
For Parallel: create separate task trees per independent issue

Read the full file on GitHub · 112 lines

Files

What ships with it

14 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 112 lines · 37 tokens per session scan A 34ba9607eb34

Subscribe to this mod's changes

ck:fix is a skill published in the GitHub repository manhvann/codexkit (89 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 1,143 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Debugging

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

deck-retro

Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…

asheshgoplani/agent-deck · 86 tokens

incident-response-incident-response

Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.

rmyndharis/antigravity-skills · 36 tokens

cwv-optimizer

Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…

adobe/skills · 112 tokens