@harness-engineering/cli 1.1.1 → 1.2.0

package/dist/agents/agents/skills/claude-code/harness-verify/SKILL.md

@@ -1,122 +0,0 @@
-# Harness Verify
-
-> Binary pass/fail quick gate. Runs test, lint, typecheck — returns structured result. No judgment calls, no deep analysis. Pass or fail.
-
-## When to Use
-
-- After every task as a final sanity check
-- As the final step in any code-producing skill
-- When you need a fast mechanical answer: "does the code compile, lint, and pass tests?"
-- NOT for deep verification or architectural review (use `harness-verification` for that)
-- NOT for AI-powered code review (use `harness-code-review` for that)
-
-## Relationship to Other Skills
-
-| Skill                     | What It Does                                   | Time  |
-| ------------------------- | ---------------------------------------------- | ----- |
-| **harness-verify** (this) | Mechanical quick gate: typecheck, lint, test   | ~30s  |
-| **harness-verification**  | Deep audit: architecture, patterns, edge cases | ~5min |
-
-`harness-verify` is the fast, deterministic gate. `harness-verification` is the slow, thorough audit. They serve different purposes and should not be confused.
-
-## Process
-
-### Phase 1: DETECT
-
-Auto-detect project commands by inspecting the project root:
-
-1. **package.json** — Look for `scripts.test`, `scripts.lint`, `scripts.typecheck` (or `scripts.tsc`, `scripts.type-check`)
-2. **Makefile** — Look for `test`, `lint`, `typecheck` targets
-3. **Conventions** — Fall back to common commands:
-   - Typecheck: `npx tsc --noEmit`, `mypy .`, `go vet ./...`
-   - Lint: `npx eslint .`, `ruff check .`, `golangci-lint run`
-   - Test: `npm test`, `pytest`, `go test ./...`
-4. **Language detection** — Use file extensions to determine which convention set applies
-
-For each of the three checks (typecheck, lint, test), record either the detected command or `NONE` if no command can be determined.
-
-### Phase 2: EXECUTE
-
-Run all detected commands in this order: **typecheck -> lint -> test**.
-
-Rules:
-
-- Run ALL commands regardless of earlier failures. Do not short-circuit.
-- Capture exit code, stdout, and stderr for each command.
-- Exit code 0 = PASS. Any non-zero exit code = FAIL.
-- If a command was `NONE` (not detected), mark that check as `SKIPPED`.
-- Run each command from the project root directory.
-- Do not modify any files. Do not install dependencies. Do not fix errors.
-
-### Phase 3: REPORT
-
-Output a structured result in this exact format:
-
-```
-Verification: [PASS/FAIL]
-- Typecheck: [PASS/FAIL/SKIPPED]
-- Lint:      [PASS/FAIL/SKIPPED]
-- Test:      [PASS/FAIL/SKIPPED]
-```
-
-Rules:
-
-- Overall `Verification: PASS` only if all non-skipped checks passed.
-- If all checks are SKIPPED, overall result is `PASS` (nothing to fail).
-- On FAIL, include a brief summary of what failed (e.g., "3 type errors", "2 lint errors", "5 tests failed") below the structured block.
-
-## Deterministic Checks
-
-This skill is entirely deterministic. There are no LLM judgment calls anywhere in the process.
-
-- Exit code 0 = PASS. Always.
-- Exit code non-zero = FAIL. Always.
-- No "it looks like this might be okay" reasoning. No interpretation of output.
-- The same codebase with the same commands will always produce the same result.
-
-## Harness Integration
-
-- Follows Principle 7 (Deterministic-vs-LLM Split) — this skill is entirely deterministic
-- Invoked as the final step by code-producing skills (harness-execution, harness-tdd)
-- Complements harness-verification (deep audit) — use verify for quick checks, verification for milestones
-- Output format is consumed by harness-integrity for the unified pipeline
-
-## Success Criteria
-
-- [ ] All detected commands were executed
-- [ ] Report follows the structured format exactly
-- [ ] Overall verdict correctly reflects individual results
-- [ ] Failed checks include error output summary
-
-## Examples
-
-### Example: Node.js Project
-
-```
-Verification: PASS
-- Types: PASS (no errors)
-- Lint: PASS (0 warnings)
-- Tests: PASS (42/42)
-```
-
-### Example: Failing Project
-
-```
-Verification: FAIL
-- Types: FAIL (3 type errors in src/auth/login.ts)
-- Lint: PASS
-- Tests: NOT RUN
-```
-
-## Gates
-
-- **No judgment calls.** The exit code is the only signal.
-- **No skipping.** If a command is detected, it runs. Period.
-- **Fresh execution only.** Do not cache results. Do not reuse previous runs. Execute the commands right now.
-- **No file modifications.** This skill is read-only (plus command execution). It must not change the codebase.
-
-## Escalation
-
-- **Timeout:** Each command has a 120-second timeout. If a command exceeds this, mark it as FAIL with reason "TIMEOUT".
-- **No commands detected:** If no typecheck, lint, or test commands can be detected, all three checks are SKIPPED and the overall result is PASS. Log a note that no verification commands were found.
-- **Environment errors:** If a command fails due to missing tooling (e.g., `tsc` not installed), mark it as FAIL. Do not attempt to install the tooling.

package/dist/agents/agents/skills/claude-code/harness-verify/skill.yaml

@@ -1,40 +0,0 @@
-name: harness-verify
-version: "1.0.0"
-description: Binary pass/fail quick gate — runs test, lint, typecheck commands and returns structured result
-triggers:
-  - manual
-  - on_task_complete
-platforms:
-  - claude-code
-  - gemini-cli
-tools:
-  - Bash
-  - Read
-  - Glob
-cli:
-  command: harness skill run harness-verify
-  args:
-    - name: path
-      description: Project root path
-      required: false
-mcp:
-  tool: run_skill
-  input:
-    skill: harness-verify
-    path: string
-type: rigid
-cognitive_mode: meticulous-verifier
-phases:
-  - name: detect
-    description: Auto-detect project commands from package.json, Makefile, or conventions
-    required: true
-  - name: execute
-    description: Run test, lint, typecheck commands
-    required: true
-  - name: report
-    description: Return structured pass/fail result
-    required: true
-state:
-  persistent: false
-  files: []
-depends_on: []

package/dist/agents/agents/skills/claude-code/initialize-harness-project/SKILL.md

@@ -1,200 +0,0 @@
-# Initialize Harness Project
-
-> Scaffold a new harness-compliant project or migrate an existing project to the next adoption level. Assess current state, configure personas, generate AGENTS.md, and validate the result.
-
-## When to Use
-
-- Starting a brand new project that should be harness-managed from day one
-- Migrating an existing project to harness for the first time
-- Upgrading an existing harness project from one adoption level to the next (basic to intermediate, intermediate to advanced)
-- When `on_project_init` triggers fire
-- NOT when the project is already at the desired adoption level (use harness-onboarding to orient instead)
-- NOT when adding a single component to an existing harness project (use add-harness-component)
-- NOT when the project has no clear owner or maintainer — harness setup requires someone to own the constraints
-
-## Process
-
-### Phase 1: ASSESS — Determine Current State
-
-1. **Check for existing harness configuration.** Look for `.harness/` directory, `AGENTS.md`, `harness.yaml`, and any skill definitions. Their presence determines whether this is a new project or a migration.
-
-2. **For new projects:** Gather project context — language, framework, test runner, build tool. Ask the human if any of these are undecided. Do not assume defaults.
-
-3. **For existing projects:** Run `harness validate` to see what is already configured and what is missing. Read `AGENTS.md` if it exists. Identify the current adoption level:
-   - **Basic:** Has `AGENTS.md` and `harness.yaml` with project metadata. No layers, no skills, no dependency constraints.
-   - **Intermediate:** Has layers defined, dependency constraints between layers, at least one custom skill. `harness check-deps` runs and passes.
-   - **Advanced:** Has full persona configuration, custom skills for the team's workflows, state management, learnings capture, and CI integration for `harness validate`.
-
-4. **Recommend the target adoption level.** For new projects, start with basic unless the team has harness experience. For existing projects, recommend one level up from current. Present the recommendation and wait for confirmation.
-
-### Phase 2: SCAFFOLD — Generate Project Structure
-
-1. **Run `harness init` with the appropriate flags:**
-   - New basic project: `harness init --level basic --framework <framework>`
-   - New intermediate project: `harness init --level intermediate --framework <framework>`
-   - Migration to intermediate: `harness init --level intermediate --migrate`
-   - Migration to advanced: `harness init --level advanced --migrate`
-
-2. **Review generated files.** `harness init` creates:
-   - `harness.yaml` — Project configuration (name, stack, adoption level)
-   - `.harness/` directory — State and learnings storage
-   - `AGENTS.md` — Agent instructions (template, needs customization)
-   - Layer definitions (intermediate and above)
-   - Dependency constraints (intermediate and above)
-
-3. **Do not blindly accept generated content.** Read the generated `AGENTS.md` and `harness.yaml`. Flag anything that looks wrong or incomplete. The scaffolded output is a starting point, not a finished product.
-
-### Phase 3: CONFIGURE — Customize for the Project
-
-1. **Configure personas.** Run `harness persona generate` to create persona definitions based on the project's stack and team structure. Personas define how agents should behave in this project — coding style, communication preferences, constraint strictness.
-
-2. **Customize AGENTS.md.** The generated template needs project-specific content:
-   - Project description and purpose
-   - Architecture overview (components, layers, data flow)
-   - Key conventions the team follows
-   - Known constraints and forbidden patterns
-   - Links to relevant documentation
-
-3. **For intermediate and above:** Define layer boundaries. Which modules belong to which layers? What are the allowed import directions? Document these in `harness.yaml` and ensure they match the actual codebase structure.
-
-4. **For advanced:** Configure state management (`.harness/state.json` schema), learnings capture (`.harness/learnings.md` conventions), and CI integration hooks.
-
-### Phase 4: VALIDATE — Confirm Everything Works
-
-1. **Run `harness validate`** to verify the full configuration. This checks:
-   - `harness.yaml` schema validity
-   - `AGENTS.md` presence and required sections
-   - Layer definitions (if intermediate+)
-   - Dependency constraints (if intermediate+)
-   - Persona configuration (if configured)
-
-2. **Fix any validation errors before finishing.** Do not leave the project in a half-configured state.
-
-3. **Run `harness check-deps`** (intermediate and above) to verify dependency constraints match the actual codebase. If there are violations, decide with the human: update the constraints or fix the code.
-
-4. **Commit the initialization.** All generated and configured files in a single commit.
-
-## Harness Integration
-
-- **`harness init --level <level> --framework <framework>`** — Scaffold a new project at the specified adoption level.
-- **`harness init --level <level> --migrate`** — Migrate an existing project to the next adoption level, preserving existing configuration.
-- **`harness persona generate`** — Generate persona definitions based on project stack and team structure.
-- **`harness validate`** — Verify the full project configuration is valid and complete.
-- **`harness check-deps`** — Verify dependency constraints match the actual codebase (intermediate and above).
-
-## Success Criteria
-
-- `harness.yaml` exists and passes schema validation
-- `AGENTS.md` exists with project-specific content (not just the template)
-- `.harness/` directory exists with appropriate state files
-- `harness validate` passes with zero errors
-- `harness check-deps` passes (intermediate and above)
-- Personas are configured if the project uses them
-- The adoption level matches what was agreed upon with the human
-- All generated files are committed in a single atomic commit
-
-## Examples
-
-### Example: New TypeScript Project (Basic Level)
-
-**ASSESS:**
-
-```
-Human: "I'm starting a new TypeScript API project using Express and Vitest."
-Check for .harness/ — not found. This is a new project.
-Recommend: basic level (new project, start simple).
-Human confirms: "Basic is fine for now."
-```
-
-**SCAFFOLD:**
-
-```bash
-harness init --level basic --framework express
-# Creates: harness.yaml, .harness/, AGENTS.md (template)
-```
-
-**CONFIGURE:**
-
-```
-Edit AGENTS.md:
-  - Add project description: "REST API for widget management"
-  - Add stack: TypeScript, Express, Vitest, PostgreSQL
-  - Add conventions: "Use zod for validation, repository pattern for data access"
-  - Add constraints: "No direct SQL queries outside repository layer"
-```
-
-**VALIDATE:**
-
-```bash
-harness validate  # Pass — basic level checks satisfied
-git add harness.yaml .harness/ AGENTS.md
-git commit -m "feat: initialize harness project at basic level"
-```
-
-### Example: Migrating Existing Project from Basic to Intermediate
-
-**ASSESS:**
-
-```
-Read harness.yaml — level: basic
-Read AGENTS.md — exists, has project-specific content
-Run: harness validate — passes at basic level
-Recommend: intermediate (add layers and dependency constraints)
-Human confirms: "Yes, we're ready for layers."
-```
-
-**SCAFFOLD:**
-
-```bash
-harness init --level intermediate --migrate
-# Preserves existing harness.yaml and AGENTS.md
-# Adds: layer definitions template, dependency constraints template
-```
-
-**CONFIGURE:**
-
-```
-Define layers in harness.yaml:
-  - presentation: src/routes/, src/middleware/
-  - business: src/services/, src/models/
-  - data: src/repositories/, src/db/
-
-Define constraints:
-  - presentation → business (allowed)
-  - business → data (allowed)
-  - data → presentation (forbidden)
-  - presentation → data (forbidden — must go through business)
-
-Update AGENTS.md with layer documentation.
-```
-
-**VALIDATE:**
-
-```bash
-harness validate      # Pass — intermediate level checks satisfied
-harness check-deps    # Pass — no constraint violations in existing code
-git add -A
-git commit -m "feat: migrate harness project to intermediate level with layers"
-```
-
-### Example: Adoption Level Progression
-
-**Basic (start here):**
-
-- `AGENTS.md` with project context
-- `harness.yaml` with metadata
-- `harness validate` runs in development
-
-**Intermediate (add structure):**
-
-- Layer definitions and boundaries
-- Dependency constraints enforced by `harness check-deps`
-- At least one custom skill for team workflows
-
-**Advanced (full integration):**
-
-- Persona configuration for consistent agent behavior
-- State management across sessions
-- `.harness/learnings.md` capturing institutional knowledge
-- `harness validate` runs in CI pipeline
-- Custom skills for all common team workflows

package/dist/agents/agents/skills/claude-code/initialize-harness-project/skill.yaml

@@ -1,31 +0,0 @@
-name: initialize-harness-project
-version: "1.0.0"
-description: Scaffold a new harness-compliant project
-cognitive_mode: constructive-architect
-triggers:
-  - manual
-  - on_project_init
-platforms:
-  - claude-code
-  - gemini-cli
-tools:
-  - Bash
-  - Read
-  - Write
-  - Glob
-cli:
-  command: harness skill run initialize-harness-project
-  args:
-    - name: path
-      description: Project root path
-      required: false
-mcp:
-  tool: run_skill
-  input:
-    skill: initialize-harness-project
-    path: string
-type: flexible
-state:
-  persistent: false
-  files: []
-depends_on: []

package/dist/agents/agents/skills/claude-code/validate-context-engineering/SKILL.md

@@ -1,129 +0,0 @@
-# Validate Context Engineering
-
-> Validate AGENTS.md quality and evolve it as the codebase changes. Good context engineering means AI agents always have accurate, current knowledge about the project.
-
-## When to Use
-
-- After adding new files, modules, or packages to the project
-- After renaming, moving, or deleting significant files
-- After changing public APIs, architectural patterns, or conventions
-- When onboarding a new contributor (human or AI) and want to verify context is current
-- When `on_context_check` or `on_pre_commit` triggers fire
-- Periodically (weekly or per-sprint) as a hygiene check
-- NOT when making trivial changes (typo fixes, comment updates, formatting)
-- NOT during active feature development — run this between features or at cycle boundaries
-
-## Process
-
-### Phase 1: Audit — Run Automated Checks
-
-1. **Run `harness validate`** to check overall project health. Review any context-related warnings or errors in the output.
-
-2. **Run `harness check-docs`** to detect documentation gaps, broken links, and stale references. Capture the full output for analysis.
-
-3. **Review AGENTS.md manually.** Automated tools catch structural issues but miss semantic drift. Read each section and ask: "Is this still true?"
-
-### Phase 2: Detect Gaps
-
-Categorize findings into four types:
-
-1. **Undocumented files.** New source files, modules, or packages that are not mentioned in AGENTS.md or any knowledge map section. These are the highest priority — an AI agent encountering these files has no context.
-
-2. **Broken links.** References to files, functions, or URLs that no longer exist. These actively mislead agents.
-
-3. **Stale sections.** Content that was accurate when written but no longer reflects reality. Examples: renamed functions still referenced by old name, removed features still described, changed conventions not updated.
-
-4. **Missing context.** Sections that exist but lack critical information. A module is listed but its purpose, constraints, or relationships are not explained. An AI agent can find the file but does not understand why it exists or how to use it correctly.
-
-### Phase 3: Suggest Updates
-
-For each gap, generate a specific suggestion:
-
-- **Undocumented files:** Draft a new section or entry with the file path, purpose, key exports, and relationship to existing modules. Use the existing AGENTS.md style and structure.
-- **Broken links:** Identify the correct target (renamed file, moved function) or recommend removal if the target was deleted.
-- **Stale sections:** Draft replacement text that reflects current reality. Show the diff between old and new.
-- **Missing context:** Draft additional content that fills the gap. Focus on what an AI agent needs to know: purpose, constraints, relationships, and gotchas.
-
-### Phase 4: Apply with Approval
-
-1. **Present all suggestions as a grouped list.** Organize by section of AGENTS.md for easy review.
-
-2. **Apply approved changes.** Update AGENTS.md with the approved suggestions. Preserve existing formatting and style.
-
-3. **Re-run `harness check-docs`** to verify all fixes are clean. No new issues should be introduced.
-
-4. **Commit the update.** Use a descriptive commit message that summarizes what was updated and why.
-
-## What Makes Good AGENTS.md Content
-
-Good context engineering treats AGENTS.md as a **dynamic knowledge base**, not a static document.
-
-- **Accuracy over completeness.** A small, accurate AGENTS.md is better than a comprehensive but stale one. Every statement must be verifiable against the current codebase.
-- **Purpose-first descriptions.** Do not just list files. Explain WHY each module exists, what problem it solves, and what constraints apply to it.
-- **Relationship mapping.** Show how modules connect. Which modules depend on which? What are the boundaries? An agent reading one section should understand how it fits into the whole.
-- **Gotchas and constraints.** Document the non-obvious. What will break if someone does X? What patterns must be followed? What is forbidden and why?
-- **Change-friendly structure.** Organize so that adding a new module means adding one section, not updating ten places. Use consistent formatting so automated tools can parse it.
-- **Actionable guidance.** Every section should help an agent make correct decisions. "This module handles authentication" is less useful than "This module handles authentication. All auth changes must go through the AuthService class. Direct database access for auth data is forbidden — use the repository layer."
-
-## Harness Integration
-
-- **`harness validate`** — Full project health check. Reports context gaps as part of overall validation.
-- **`harness check-docs`** — Focused documentation audit. Detects broken links, missing references, stale sections, and undocumented files.
-- **`harness fix-drift`** — Auto-fix simple drift issues (broken links, renamed references). Use after manual review confirms the fixes are correct.
-
-## Success Criteria
-
-- `harness check-docs` passes with zero errors and zero warnings
-- Every source file that contains public API or architectural significance is referenced in AGENTS.md
-- All file paths and function names in AGENTS.md match the current codebase
-- All links (internal and external) resolve correctly
-- AGENTS.md sections accurately describe current module purposes, constraints, and relationships
-- A new AI agent reading AGENTS.md can navigate the codebase and make correct decisions without additional guidance
-
-## Examples
-
-### Example: New module added but not documented
-
-**Audit output from `harness check-docs`:**
-
-```
-WARNING: Undocumented file detected: src/services/notification-service.ts
-  - File contains 3 public exports: NotificationService, NotificationType, sendNotification
-  - File is imported by 4 other modules
-  - No AGENTS.md section references this file
-```
-
-**Suggested update:**
-
-```markdown
-### Notification Service (`src/services/notification-service.ts`)
-
-Handles all outbound notifications (email, Slack, webhook). All notification delivery
-must go through `NotificationService` — direct use of transport libraries (nodemailer,
-Slack SDK) outside this module is forbidden.
-
-- `NotificationType` — enum of supported notification channels
-- `sendNotification()` — primary entry point; routes to the correct transport
-- Requires `NOTIFICATION_CONFIG` environment variables to be set
-- Respects rate limits defined in `harness.config.json` under `notifications`
-```
-
-**Apply:** Add the section under the Services heading in AGENTS.md. Re-run `harness check-docs` to confirm the warning is resolved.
-
-### Example: Renamed function still referenced by old name
-
-**Audit output:**
-
-```
-ERROR: Broken reference in AGENTS.md line 47: `calculateShipping()`
-  - Function was renamed to `computeShippingCost()` in commit abc123
-  - Located in src/services/shipping.ts
-```
-
-**Fix:** Replace `calculateShipping()` with `computeShippingCost()` in AGENTS.md. Verify no other references to the old name exist.
-
-## Escalation
-
-- **When AGENTS.md is severely outdated (>20 issues):** Do not attempt to fix everything at once. Prioritize: broken links first, then undocumented public APIs, then stale descriptions. Batch the work across multiple commits.
-- **When you are unsure whether a section is stale:** Check git blame for the section and compare against recent changes to the referenced files. If the section has not been updated since the referenced files changed, it is likely stale.
-- **When the project has no AGENTS.md:** Escalate to the human. Creating an AGENTS.md from scratch is a significant decision about project structure and should be done intentionally, not automatically.

package/dist/agents/agents/skills/claude-code/validate-context-engineering/skill.yaml

@@ -1,31 +0,0 @@
-name: validate-context-engineering
-version: "1.0.0"
-description: Validate repository context engineering practices (AGENTS.md, doc coverage, knowledge map)
-cognitive_mode: meticulous-verifier
-triggers:
-  - manual
-  - on_pr
-  - on_commit
-platforms:
-  - claude-code
-  - gemini-cli
-tools:
-  - Bash
-  - Read
-  - Glob
-cli:
-  command: harness skill run validate-context-engineering
-  args:
-    - name: path
-      description: Project root path
-      required: false
-mcp:
-  tool: run_skill
-  input:
-    skill: validate-context-engineering
-    path: string
-type: flexible
-state:
-  persistent: false
-  files: []
-depends_on: []