@harness-engineering/cli 1.4.0 → 1.6.1

package/dist/agents/personas/architecture-enforcer.yaml

@@ -5,6 +5,7 @@ role: Enforce layer boundaries, detect circular dependencies, block forbidden im
 skills:
   - enforce-architecture
   - check-mechanical-constraints
+  - harness-dependency-health
 commands:
   - check-deps
   - validate

package/dist/agents/personas/code-reviewer.yaml

@@ -0,0 +1,43 @@
+version: 2
+name: Code Reviewer
+description: Full-lifecycle code review with harness methodology
+role: >
+  Perform AI-powered code review incorporating harness validation,
+  architectural analysis, and project-specific calibration.
+  Produces structured Strengths/Issues/Assessment output.
+skills:
+  - harness-code-review
+steps:
+  - command: validate
+    when: always
+  - command: check-deps
+    when: always
+  - command: check-docs
+    when: on_pr
+  - command: check-perf
+    when: on_pr
+  - skill: harness-code-review
+    when: on_pr
+    output: auto
+  - skill: harness-code-review
+    when: manual
+    output: auto
+triggers:
+  - event: on_pr
+    conditions:
+      paths:
+        - "src/**"
+        - "packages/**"
+  - event: on_commit
+    conditions:
+      branches:
+        - main
+        - develop
+config:
+  severity: error
+  autoFix: false
+  timeout: 600000
+outputs:
+  agents-md: true
+  ci-workflow: true
+  runtime-config: true

package/dist/agents/personas/codebase-health-analyst.yaml

@@ -0,0 +1,32 @@
+version: 1
+name: Codebase Health Analyst
+description: Proactively identifies structural problems, coupling risks, and architectural drift
+role: Run health checks, detect hotspots, analyze impact, surface risks before they become incidents
+skills:
+  - harness-hotspot-detector
+  - harness-dependency-health
+  - harness-impact-analysis
+  - cleanup-dead-code
+  - harness-perf
+  - harness-security-scan
+commands:
+  - graph status
+  - check-deps
+  - check-perf
+  - check-security
+triggers:
+  - event: scheduled
+    cron: "0 6 * * 1"
+  - event: on_pr
+    conditions:
+      min_files: 10
+  - event: manual
+config:
+  severity: warning
+  autoFix: false
+  timeout: 600000
+  securitySeverity: warning
+outputs:
+  agents-md: false
+  ci-workflow: true
+  runtime-config: true

package/dist/agents/personas/documentation-maintainer.yaml

@@ -5,9 +5,11 @@ role: Detect documentation drift, validate doc coverage, align docs with code ch
 skills:
   - detect-doc-drift
   - align-documentation
+  - harness-knowledge-mapper
 commands:
   - check-docs
   - validate
+  - scan
 triggers:
   - event: on_pr
     conditions:

package/dist/agents/personas/entropy-cleaner.yaml

@@ -5,9 +5,12 @@ role: Run scheduled cleanup, detect documentation drift, fix pattern violations
 skills:
   - cleanup-dead-code
   - detect-doc-drift
+  - harness-hotspot-detector
+  - harness-impact-analysis
 commands:
   - cleanup
   - fix-drift
+  - scan
 triggers:
   - event: scheduled
     cron: "0 6 * * 1"

package/dist/agents/personas/graph-maintainer.yaml

@@ -0,0 +1,27 @@
+version: 1
+name: Graph Maintainer
+description: Keeps the knowledge graph fresh, monitors connector health, and ensures data quality
+role: Re-scan codebase, sync external connectors, detect graph anomalies, maintain graph freshness
+skills:
+  - harness-dependency-health
+  - harness-knowledge-mapper
+  - validate-context-engineering
+commands:
+  - scan
+  - ingest
+  - graph status
+triggers:
+  - event: scheduled
+    cron: "0 4 * * *"
+  - event: on_commit
+    conditions:
+      branches: ["main"]
+  - event: manual
+config:
+  severity: warning
+  autoFix: false
+  timeout: 600000
+outputs:
+  agents-md: false
+  ci-workflow: true
+  runtime-config: true

package/dist/agents/personas/parallel-coordinator.yaml

@@ -0,0 +1,29 @@
+version: 2
+name: Parallel Coordinator
+description: Dispatches independent work across isolated Task Executor instances
+role: >
+  Verify task independence, create focused agent briefs, dispatch
+  Task Executor instances in isolated worktrees, integrate results,
+  and run full validation after all agents complete.
+skills:
+  - harness-parallel-agents
+steps:
+  - command: validate
+    when: always
+  - skill: harness-parallel-agents
+    when: manual
+    output: inline
+triggers:
+  - event: on_pr
+    conditions:
+      paths:
+        - "src/**"
+        - "packages/**"
+config:
+  severity: error
+  autoFix: false
+  timeout: 1800000
+outputs:
+  agents-md: true
+  ci-workflow: true
+  runtime-config: true

package/dist/agents/personas/performance-guardian.yaml

@@ -0,0 +1,26 @@
+version: 1
+name: Performance Guardian
+description: Enforces performance budgets and detects regressions
+role: Run structural complexity checks, coupling analysis, benchmark regression detection, and size budget enforcement on PRs and scheduled runs
+skills:
+  - harness-perf
+  - harness-tdd
+commands:
+  - check-perf
+  - perf
+triggers:
+  - event: on_pr
+    conditions:
+      paths:
+        - "src/**"
+        - "packages/**"
+  - event: scheduled
+    cron: "0 6 * * 1"
+config:
+  severity: error
+  autoFix: false
+  timeout: 300000
+outputs:
+  agents-md: true
+  ci-workflow: true
+  runtime-config: true

package/dist/agents/personas/security-reviewer.yaml

@@ -0,0 +1,35 @@
+version: 2
+name: Security Reviewer
+description: Security-focused code reviewer with OWASP/CWE expertise
+role: >
+  Identifies security vulnerabilities, enforces secure coding patterns,
+  and produces structured findings with CWE references and remediation guidance.
+skills:
+  - harness-security-review
+  - harness-code-review
+steps:
+  - command: validate
+    when: always
+  - command: check-deps
+    when: always
+  - skill: harness-security-review
+    when: on_pr
+    output: auto
+  - skill: harness-security-review
+    when: manual
+    output: auto
+triggers:
+  - event: on_pr
+    conditions:
+      paths:
+        - "src/**"
+        - "packages/**"
+  - event: manual
+config:
+  severity: error
+  autoFix: false
+  timeout: 120000
+outputs:
+  agents-md: true
+  ci-workflow: true
+  runtime-config: true

package/dist/agents/personas/task-executor.yaml

@@ -0,0 +1,41 @@
+version: 2
+name: Task Executor
+description: Executes approved plans with state tracking, TDD, and verification
+role: >
+  Execute implementation plans task-by-task using harness methodology.
+  Maintains persistent state, follows TDD rhythm, runs verification
+  after each task, and respects checkpoint protocol.
+skills:
+  - harness-execution
+steps:
+  - command: validate
+    when: always
+  - command: check-deps
+    when: always
+  - command: scan
+    when: manual
+  - skill: harness-execution
+    when: on_plan_approved
+    output: auto
+  - skill: harness-execution
+    when: manual
+    output: auto
+triggers:
+  - event: on_pr
+    conditions:
+      paths:
+        - "src/**"
+        - "packages/**"
+  - event: on_commit
+    conditions:
+      branches:
+        - main
+        - develop
+config:
+  severity: error
+  autoFix: false
+  timeout: 900000
+outputs:
+  agents-md: true
+  ci-workflow: true
+  runtime-config: true

package/dist/agents/skills/README.md

@@ -37,6 +37,14 @@ agents/skills/
 - `initialize-harness-project` - Scaffold new project
 - `add-harness-component` - Add components
 
+### Graph Integration Levels
+
+**Graph-Transformed** (7 skills): harness-code-review, validate-context-engineering, detect-doc-drift, cleanup-dead-code, harness-parallel-agents, enforce-architecture, harness-onboarding
+
+**Graph-Enhanced** (5 skills): harness-execution, harness-planning, harness-architecture-advisor, harness-refactoring, align-documentation
+
+**Graph-Enabled** (5 new skills): harness-impact-analysis, harness-dependency-health, harness-hotspot-detector, harness-test-advisor, harness-knowledge-mapper
+
 ## Usage
 
 ### Claude Code

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

@@ -73,6 +73,16 @@
 
 2. **Run `harness check-deps`** to verify no dependency violations were introduced. The new component's imports must respect layer boundaries.
 
+### Graph Refresh
+
+If a knowledge graph exists at `.harness/graph/`, refresh it after code changes to keep graph queries accurate:
+
+```
+harness scan [path]
+```
+
+Skipping this step means subsequent graph queries (impact analysis, dependency health, test advisor) may return stale results.
+
 3. **If validation fails,** fix the issues before committing. Common causes:
    - New layer not properly registered in `harness.yaml`
    - Component placed in wrong directory for its declared layer

package/dist/agents/skills/claude-code/align-documentation/SKILL.md

@@ -31,6 +31,15 @@
 
 3. **Run `harness check-docs`** to identify any documentation that already has broken references due to the changes.
 
+### Graph-Enhanced Context (when available)
+
+When a knowledge graph exists at `.harness/graph/`, use graph queries for faster, more accurate context:
+
+- `query_graph` — find `documents` edges pointing to nodes changed in this diff
+- `get_impact` — auto-suggest which docs need updating after code changes
+
+Replaces manual doc-to-code correlation. Fall back to file-based commands if no graph is available.
+
 ### Phase 2: Map — Connect Code Changes to Documentation
 
 For each changed file, identify all documentation that references it:
@@ -84,6 +93,16 @@ For each affected documentation location:
 
 4. **Run `harness fix-drift`** to catch any remaining simple drift issues that manual review missed.
 
+### Graph Refresh
+
+If a knowledge graph exists at `.harness/graph/`, refresh it after code changes to keep graph queries accurate:
+
+```
+harness scan [path]
+```
+
+Skipping this step means subsequent graph queries (impact analysis, dependency health, test advisor) may return stale results.
+
 5. **Commit the documentation update.** Use a commit message that references the original change: "docs: update AGENTS.md for notification service refactoring" or "docs: sync API docs after auth module rename."
 
 ## What to Update

package/dist/agents/skills/claude-code/cleanup-dead-code/SKILL.md

@@ -28,6 +28,15 @@
 
 3. **Review the report summary.** Note the total count and distribution. A few dead exports are normal; dozens suggest accumulated entropy from incomplete refactorings.
 
+### Graph-Enhanced Context (when available)
+
+When a knowledge graph exists at `.harness/graph/`, use graph queries for faster, more accurate dead code detection:
+
+- `query_graph` — perform graph reachability analysis from entry point nodes to identify truly unreachable code
+- `get_relationships` — distinguish dynamic imports from genuinely unused code by checking edge types
+
+Graph reachability reduces false positives compared to static analysis alone, since it traces the full transitive import graph including re-exports. Fall back to file-based commands if no graph is available.
+
 ### Phase 2: Categorize — Safe vs. Needs Review
 
 **Safe to auto-fix (remove without further analysis):**
@@ -63,6 +72,16 @@ For each item categorized as safe:
 
 ### Phase 4: Report Remaining Items
 
+### Graph Refresh
+
+If a knowledge graph exists at `.harness/graph/`, refresh it after code changes to keep graph queries accurate:
+
+```
+harness scan [path]
+```
+
+Dead code removal changes graph topology — skipping this step means subsequent graph queries (impact analysis, dependency health, test advisor) may return stale results.
+
 For items that need human review, report:
 
 1. **What it is** — file path, export name, what it does

package/dist/agents/skills/claude-code/detect-doc-drift/SKILL.md

@@ -22,6 +22,14 @@
 
 3. **Optionally, run `git diff` against a baseline** (last release, last sprint, etc.) to identify which code files changed. This helps prioritize — docs for recently changed files are most likely to be drifted.
 
+### Graph-Enhanced Context (when available)
+
+When a knowledge graph exists at `.harness/graph/`, use graph queries for faster, more accurate drift detection:
+
+- `query_graph` — find `documents` edges where the target code node has changed since the doc node was last updated
+
+When a graph is available, drift is simply stale edges: doc-to-code edges where the code side has been modified more recently than the doc side. This replaces regex pattern matching and catches semantic drift that text search misses. Fall back to file-based commands if no graph is available.
+
 ### Phase 2: Identify — Classify Drift Types
 
 Categorize each finding into one of these drift types:

package/dist/agents/skills/claude-code/enforce-architecture/SKILL.md

@@ -28,6 +28,15 @@
    - Same-layer imports may or may not be allowed depending on project config
    - Cross-cutting concerns (logging, config) have their own rules
 
+### Graph-Enhanced Context (when available)
+
+When a knowledge graph exists at `.harness/graph/`, use graph queries for faster, more accurate violation detection:
+
+- `query_graph` — traverse `imports` edges against layer constraint nodes to find all violations in a single query
+- `get_relationships` — find all code dependent on a violation target to show the full scope of impact
+
+Graph queries show the complete violation scope (not just the first occurrence per file) and reveal transitive violations that single-file analysis misses. Fall back to file-based commands if no graph is available.
+
 ### Phase 2: Run Dependency Checks
 
 1. **Run `harness check-deps`** to analyze all import statements against the constraint model. Capture the full JSON output.

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

@@ -104,6 +104,15 @@ Look for existing issues that may affect the decision:
 Store analysis in: .harness/architecture/<topic>/analysis.md
 ```
 
+### Graph-Enhanced Context (when available)
+
+When a knowledge graph exists at `.harness/graph/`, use graph queries for faster, more accurate context:
+
+- `query_graph` — discover how similar features are structured in the codebase
+- `search_similar` — find analogous patterns and implementations
+
+Replaces manual Glob/Grep exploration with graph pattern discovery. Fall back to file-based commands if no graph is available.
+
 ---
 
 ### Phase 3: PROPOSE — Present Options with Trade-Offs