Skill

harness-setup

Bootstrap a repository with Harness Engineering tooling: detect stack (TS/Go/Proto/mixed), install config templates (biome.json, .golangci.yml, .go-arch-lint.yml, buf.yaml, lefthook.yml), copy a pointer-style CLAUDE.md, and wire up .claude/review-profile.yaml. Use this when the user says 'set up harness', 'bootstrap the repo', 'add harness engineering', or runs /harness:init. Do NOT use for modifying existing configs — that's what /harness:check is for.

Install

npx claudepluginhub toru-oizumi/claude-harness-engineering --plugin harness-engineering

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Bootstrap a repository with Harness Engineering guardrails. This is the canonical "get started" workflow. Run it once per repo.

Supporting Assets

gotchas.md

SKILL.md

Similar Skills

design-system

Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.

team-skills-platform

163.7k

ui-demo

Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.

team-skills-platform

163.7k

kotlin-patterns

Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.

team-skills-platform

163.7k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitApr 14, 2026

Actions

View Source View Plugin View on GitHub View README

Harness Setup

Bootstrap a repository with Harness Engineering guardrails. This is the canonical "get started" workflow. Run it once per repo.

When to Use

User explicitly asks to bootstrap a repo with harness tooling
User runs /harness:init
New repo is being initialized and needs guardrails from day 1

When NOT to Use

Modifying an existing harness config (the pre-config-protect hook blocks that anyway; this is intentional)
Adding a single language to an existing mixed-stack repo (use /harness:add-proto etc. instead)
Debugging why a linter isn't running (use /harness:check)

Workflow

Phase 1 — Detect stack

Check the repo for these marker files and record which are present:

Marker	Stack
`tsconfig.json` or `package.json`	TypeScript
`go.mod`	Go
`*.proto` files (anywhere) or `buf.yaml`	Proto

A repo may be any combination of these. Report the detected stack to the user before proceeding.

Phase 2 — Copy CLAUDE.md

Copy ${CLAUDE_PLUGIN_ROOT}/templates/CLAUDE.md.template to the repo root as CLAUDE.md.

IMPORTANT constraints:

The template is intentionally under 50 lines (based on IFScale primacy bias research — more instructions make Claude less responsive to any single instruction)
It uses pointer style: instead of embedding rules, it points to rules/general/*.md and skill names
If a CLAUDE.md already exists, ASK the user before overwriting. Offer to diff the two.

Phase 3 — Install language-specific configs

Per detected stack, copy these templates:

TypeScript:

templates/biome.json → <repo>/biome.json
templates/review-profile.typescript.yaml → <repo>/.claude/review-profile.yaml (or merge if exists)

Go:

templates/.go-arch-lint.clean-arch.yml → <repo>/.go-arch-lint.yml
A .golangci.yml matching the user's preference (ask: strict / moderate / lenient)
templates/review-profile.go.yaml → <repo>/.claude/review-profile.yaml

Proto:

templates/buf.yaml → <repo>/buf.yaml (if none exists)
templates/review-profile.proto.yaml → <repo>/.claude/review-profile.yaml

Phase 4 — Install lefthook

Copy templates/lefthook.yml to the repo root. Run lefthook install if the user has lefthook installed; otherwise instruct them to brew install lefthook first.

Phase 5 — Verify

Suggest running /harness:check to verify everything is wired up correctly.

Important Notes

The pre-config-protect hook will start blocking edits to biome.json, .golangci.yml, etc. immediately after they're created. If the user needs to tune these, they must edit manually from outside Claude Code.
For mixed-stack repos (e.g., Go backend + TypeScript frontend), create one .claude/review-profile.yaml per service directory is supported but advanced — default to a single root profile for v0.1.

Related Skills

ts-stack, go-stack, proto-stack — stack-specific details
config-protect — why linter configs are write-protected
edit-lint-feedback-loop — how the hook infrastructure works

Gotchas

See gotchas.md in this directory.