agentleFS
daikubo-jbdaikubo-jb/my-claude-harness/skills/harness-review/SKILL.md

harness-review

Skill0 starsChanged 2 months agoMITView on GitHub

doc-storage の worklog から「ハーネスへの示唆」を横断して読み、ハーネスの昇格・削除・追加を提案する。手動で起動する。

12 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ecosystem-reference, fractal-delegation and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • naman10parikhSkill

    ecosystem-reference

    Quick-access directory of Claude Code ecosystem repos, skills, plugins, MCPs, and patterns. Use when improving the harness.

    Also in 5 projects that use this

  • naman10parikhSkill

    fractal-delegation

    Also in 5 projects that use this

  • KirchliveSkill

    skill-routing

    Decides which of the installed skills a task needs and loads them before the work starts. This skill should be used at the beginning of any multi-step task — build, fix, refactor, migrate, review, plan, release, research, write, design, video — and again at every phase change, after context compaction, and when work moves into a different part of the codebase. Use it for requests like "let's build X", "fix this bug", "refactor Y", "plan the migration", "review this", and also when the user asks which skill applies, why a skill did not fire, or asks to check what is available.

    Also in 5 projects that use this

  • sublimotionSkill

    agent-runtime

    Launch and manage detached agent runs on EKS via the agent-runner CLI. Use when the user says "launch an agent run", "agent runtime", "agent-runner", "run this spec on the cluster", "check run status", "agent run logs", or "stop a run". Do NOT use for writing the agent-runner code itself (edit the sibling ../agent-runner repo), Terraform of the foundation (use terraform-automation), or GPU serving deployments (use infra-deployer).

    Also in 5 projects that use this

  • GoZippySkill

    repo-scout

    Also in 5 projects that use this

  • botirkhaltaevSkill

    design-systems

    Build and maintain scalable design systems: design tokens, component libraries, naming conventions, governance, and design-to-code pipelines. Covers Figma variables, token architecture, atomic design, component APIs, versioning, and team workflows. Use when creating a design system, scaling an existing one, or establishing design-engineering alignment. Triggers on: "design system", "design tokens", "component library", "token naming", "Figma variables", "atomic design", "design ops", "design-to-code".

    Also in 5 projects that use this

  • +6 more from naman10parikh

The file

Files
SKILL.md

$ARGUMENTS

ハーネス(my-claude-harness)を運用ログから直す。月1回か10セッションごとに手で起動する。 ここがハーネスを変更する唯一の入口。 作業中のセッションでは書き換えない。

1. 読む

doc-storage の全プロジェクトの claude-doc/worklog/ から「ハーネスへの示唆」欄だけを 横断して読む。ルートは skill: doc-storage。対象期間は引数で指定が無ければ前回のレビュー以降。

worklog 以外(plans / reviews)は読まない。示唆欄に書かれていないことは材料にしない。 記憶や印象で補わない。

2. 3分類で提案する

分類条件提案の中身
昇格同じ文言ルールが2回以上破られたhook か permissions.deny に落とす。具体的な設定・スクリプトの差分まで書く
削除一度も効いた記録が無い / モデル更新で不要になった削除する行
追加同じ事故を繰り返した検査 hook か run-* skill。文言は最後の手段

各提案に、根拠にした worklog のパスと日付を必ず添える。根拠が1件しかないものは 「1件のみ」と明記する。

Claude Code の自動メモリ(~/.claude/projects/*/memory/)に同じ指摘が2回以上 溜まっているものも昇格の対象。メモリは個人・一時の置き場、ハーネスは公開リポの昇格先。

3. 歯止め

  • 削除の提案がゼロのレビューは疑う。 増える一方なら、効いていないルールを見落としている。 ゼロのまま出すなら、なぜ削れるものが無いのかを1文で書く
  • 文言を足す提案は、hook にも deny にもできない理由を書けるときだけ出す
  • 1回のレビューで出す提案は多くて5件。多いなら重大な順に絞る

4. 適用

提案を一覧で提示し、ユーザーが採用を選んだものだけ適用する。全採用を前提にしない。

適用したら bash scripts/verify-harness.sh を通す。落ちたら直す。 コミットはしない。 差分を示して人に渡す。

./install.sh の再実行が要る変更(ファイルの追加・削除、設定の変更)なら、 その旨を最後に伝える。

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.