Русский

codeharness

codeharness is the shared rule set for Claude Code across projects — a source of templates, not a regular application repository. It defines how Claude should behave in any project that adopts it: when to plan before acting, when to open an issue, how to commit, how to keep state alive across sessions, and where to route a task (inline / skill / agent).

It is not meant to be dropped into a project verbatim. Every consuming project adapts it — trims what doesn't apply, extends what's missing.

Why it exists

Putting every rule into one CLAUDE.md doesn't scale — the file gets huge and Claude has to load all of it, all the time, for every task. codeharness splits the rule set in two layers instead:

• Core (CLAUDE.md) — always loaded. A short router table ("if you're about to do X, open file Y first") plus the handful of rules that apply to every task: the plan → consent → work → verification cycle, language, commits/push, persistent memory, secrets.
• Topic files (.ai-workflow/*.md) — loaded on demand, only when the router table points at them. This is progressive disclosure: detail exists, but it doesn't cost context until it's actually relevant.

The router table lives in CLAUDE.md §0 and is the single entry point — see File Map for the full table with links to every rule file.

Who it's for

Anyone maintaining multiple projects with Claude Code who wants consistent agent behavior — issue discipline, commit hygiene, session handoff, secrets handling — without hand-writing the same rules in every repo's CLAUDE.md.

Quick start

1. Read File Map to see what topics codeharness covers and where each lives in the source repository.
2. Read Setup for how to bring codeharness into a new project (copying/adapting CLAUDE.md and .ai-workflow/, project-specific tuning). Note: the exact attach mechanism is still being worked out upstream — Setup explains the current manual approach.
3. Read Process for the working cycle codeharness enforces: plan → consent → issue → work → verification → review, SemVer versioning, and task routing.

Status

codeharness versions itself using its own versioning.md rule: single source of truth is the VERSION file, current release documented in CHANGELOG.md (check there so the wiki does not lag behind each bump).

CLAUDE.md and .ai-workflow/*.md are currently Russian-only — this is a documented temporary state (see documentation.md); an English migration is planned as a separate, deliberate batch, not a silent rewrite.

Where the canon lives

This wiki is onboarding material, not the rulebook. The actual normative text lives in the codeharness git repository:

• Core: CLAUDE.md
• Topic files: .ai-workflow/

When wiki text and repository text disagree, the repository wins — see File Map for links straight to source.