Agent Harnesses & Skills

GitKB supports five integration paths for agents:

HarnessUse whenAssets/config
Claude CodeYou want Claude-native rules, skills, and MCP tools.claude/rules/, .claude/skills/, MCP config, CLAUDE.md
CodexYou use Codex locally and want GitKB skills plus session instructions.codex/skills/, .codex/instructions/, optional $CODEX_HOME install
CursorYou use Cursor Agent mode with GitKB MCP tools and repo rules/skills.cursor/rules/, .cursor/skills/, .cursor/mcp.json
WindsurfYou use Windsurf with GitKB MCP tools and repo rules/skills.windsurf/rules/, .windsurf/skills/, MCP config
Generic MCP clientsYour assistant can connect to an MCP stdio serverMCP config that runs git-kb mcp

Skill source of truth

The canonical GitKB skill content lives under .kb/skills/. Assistant-specific directories are lightweight adapters:

.kb/skills/                    # Canonical GitKB workflows
.claude/skills/                # Claude Code forwarders/adapters
.codex/skills/                 # Codex forwarders/adapters
.cursor/skills/                # Cursor forwarders/adapters
.windsurf/skills/              # Windsurf forwarders/adapters

This layout keeps GitKB workflow behavior consistent across harnesses while allowing each assistant to load skills in the format it expects. The kb-* command-style workflows are skills now, so harnesses load them from .kb/skills/ instead of separate .claude/commands/ or .codex/commands/ directories.

Projects can also expose local skill packs through additional symlinks under the harness skill directory. In Harmony, for example, .claude/skills/atc and .codex/skills/atc point at ../../.atc/skills.

GitKB skills

Core

SkillPurpose
gitkbCore KB operations, CLI/MCP mapping, workspace workflow

Task workflow

SkillPurpose
kb-boardView the kanban board with task status columns
kb-tasksList and filter tasks with relationships and status details
kb-startStart a task, load context, set it active, and check it out
kb-progressAdd dated progress entries to a task
kb-reviewReview acceptance criteria against current code/docs state
kb-closeComplete a task with evidence before status changes

Knowledge management

SkillPurpose
kb-createCreate tasks, incidents, specs, notes, and context documents
kb-searchSearch documents and suggest next actions
kb-contextLoad and validate project context before work
kb-statusInspect pending KB workspace changes
kb-commitValidate and commit KB workspace changes
kb-handoffCapture end-of-session state for the next agent

Code intelligence

SkillPurpose
code-intelligencePrefer structured symbol/call graph tools over grep
exploreFind where concepts live across code and documents
understandAnalyze a file or symbol’s structure and dependencies
refactor-safetyCheck callers, callees, and blast radius before refactors

Mutating skills such as kb-create and kb-commit should be explicit user actions. Read-only or analysis skills can be used opportunistically by agents when they need context.

Setup commands

# Claude Code integration
git kb init claude

# Codex integration
git kb init codex
git kb init codex --install-home

# Cursor integration
git kb init cursor

# Windsurf integration
git kb init windsurf

# Generic MCP clients
git kb mcp

Use git kb init <harness> --dry-run before writing files if you want to preview generated assets. Generic MCP clients use manual MCP configuration that starts git-kb mcp.

Choosing a path

  • Use Claude Code or Codex when you want assistant-native skills and workflow instructions.
  • Use Cursor when you want Cursor Agent mode to use the same GitKB MCP tools.
  • Use Windsurf when you want Windsurf to load the same GitKB rules and skills.
  • Use generic MCP when the assistant only needs tool access and you will provide workflow instructions separately.
  • MCP Setup — Connect any MCP-compatible assistant.
  • Claude Code — Claude-specific scaffold and workflow.
  • Codex — Codex-specific scaffold and global install.
  • Agent Workflows — How agents use GitKB during real work.
  • CLI Reference — Full command help for the installed CLI.