Ck:Fix logo

Ck:Fix

Community
manhvann
ck:fix

ALWAYS activate this skill before fixing ANY bug, error, test failure, CI/CD issue, type error, lint, log error, UI issue, code problem.

Overview

Publishermanhvann
Repositorycodexkit
Skill nameck:fix
Stars
88
Forks
81
Bundled files
14
LicenseMIT
Links
  • 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.

  • 14 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by manhvann on GitHub. Read the source before you install it.

Installation

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

1

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.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/manhvann/codexkit/tree/main/.agents/skills/fix
  4. 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.
2

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/manhvann/codexkit.git /tmp/codexkit
mkdir -p .claude/skills
cp -r /tmp/codexkit/.agents/skills/fix .claude/skills/manhvann-ck-fix
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ck:Fix 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 Ck:Fix 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 Ck:Fix 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.

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:

OptionRecommend WhenBehavior
Autonomous (default)Simple/moderate issuesAuto-approve if score >= 9.5 & 0 critical
Human-in-the-loop ReviewCritical/production codePause for approval at each step
QuickType errors, lint, trivial bugsFast 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.

LevelIndicatorsWorkflow
SimpleSingle file, clear error, type/lintreferences/workflow-quick.md
ModerateMulti-file, root cause unclearreferences/workflow-standard.md
ComplexSystem-wide, architecture impactreferences/workflow-deep.md
Parallel2+ independent issues OR --parallel flagParallel 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

Step 4: Fix Implementation & Verification

  • Implement fix per selected workflow, updating Tasks as phases complete.
  • Prefer multiple scout agents to verify no regressions when available.
  • Prevent future issues by adding comprehensive validation.

Step 5: Finalize (MANDATORY - never skip)

  1. Report summary: confidence score, changes, files
  2. Prefer docs_manager subagent → update the configured docs path if changes warrant
  3. Update task state/checklists and mark all tracked tasks completed
  4. Ask user if they want to commit via git_manager subagent

IMPORTANT: Skill/Subagent Activation Matrix

See references/skill-activation-matrix.md for complete matrix.

Always activate: ck:debug (all workflows) Conditional: ck:problem-solving, ck:sequential-thinking, ck:brainstorm, ck:context-engineering Subagents: debugger, researcher, planner, code_reviewer, tester, Bash Parallel: Multiple Explore agents for scouting, Bash agents for verification

Output Format

Unified step markers:

✓ Step 0: [Mode] selected - [Complexity] detected
✓ Step 1: Root cause identified - [summary]
✓ Step 2: Fix implemented - [N] files changed
✓ Step 3: Tests [X/X passed]
✓ Step 4: Review [score]/10 - [status]
✓ Step 5: Complete - [action taken]

References

Load as needed:

  • references/mode-selection.md - Prompt format for mode
  • references/complexity-assessment.md - Classification criteria
  • references/task-orchestration.md - Native Codex Task patterns for moderate+ workflows
  • references/workflow-quick.md - Quick: debug → fix → review
  • references/workflow-standard.md - Standard: full pipeline with Tasks
  • references/workflow-deep.md - Deep: research + brainstorm + plan with Tasks
  • references/review-cycle.md - Review logic (autonomous vs HITL)
  • references/skill-activation-matrix.md - When to activate each skill
  • references/parallel-exploration.md - Parallel Explore/Bash/Task coordination patterns

Specialized Workflows:

  • references/workflow-ci.md - GitHub Actions/CI failures
  • references/workflow-logs.md - Application log analysis
  • references/workflow-test.md - Test suite failures
  • references/workflow-types.md - TypeScript type errors
  • references/workflow-ui.md - Visual/UI issues (requires design skills)

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Ck:Fix AI skill do?

ALWAYS activate this skill before fixing ANY bug, error, test failure, CI/CD issue, type error, lint, log error, UI issue, code problem.

Why use Ck:Fix on TypingMind?

Because you install it once and use it with any model. Ck:Fix 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 Ck:Fix in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/manhvann/codexkit/tree/main/.agents/skills/fix. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Ck:Fix?

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 Ck:Fix?

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

Is the Ck:Fix AI skill free?

Yes. It is published on GitHub by manhvann 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

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇