@crewpilot/agent 2.0.0 → 3.0.0

package/prompts/copilot-instructions.md

@@ -1,36 +1,36 @@
-# Catalyst — Copilot Instructions
-
-This repository contains **Catalyst**, an AI Engineering Intelligence Platform built as a GitHub Copilot custom agent.
-
-## Quick Reference
-
-- **Agent router**: `.github/agents/catalyst.md` — the single source of truth for skill routing, role matrix, and guardrails
-- **Skills**: `.github/skills/*/SKILL.md` — 16 structured methodology files across 5 pillars + 3 automation skills
-- **MCP Server**: `catalyst-engine/` (CrewPilot MCP server) — TypeScript MCP server with 55 tools across 8 modules + config
-
-## How to Use
-
-Type `@catalyst` in GitHub Copilot Chat. The agent will ask for a session role (Build, Review, Plan, Design, or Just Ask), then route your requests to the appropriate skill.
-
-## Key Conventions
-
-- **Conventional commits**: `type(scope): message`
-- **Human gates**: Autopilot always pauses for approval at critical points
-- **Branch protection**: Never commit directly to `main`/`master`/`release/*`
-- **Progressive disclosure**: Summaries first, details on request
-- **Confidence gating**: Findings below threshold (default 7/10) are suppressed
-
-## Configuration
-
-`.github/catalyst.config.json` controls thresholds, pillar toggles, and per-skill overrides. See `catalyst_config_get` tool.
-
-## Architecture
-
-```
-User → @catalyst (router) → SKILL.md (methodology) → MCP tools (execution)
-                                                      ↓
-                                          SQLite (knowledge + workflows)
-                                          gh CLI (GitHub Issues/PRs)
-```
-
-For full details, see the [README](../README.md) or the [agent definition](agents/catalyst.md).
+# CrewPilot — Copilot Instructions
+
+This repository contains **CrewPilot**, an AI Engineering Intelligence Platform built as a GitHub Copilot custom agent.
+
+## Quick Reference
+
+- **Agent router**: `.github/agents/crewpilot.md` — the single source of truth for skill routing, role matrix, and guardrails
+- **Skills**: `.github/skills/*/SKILL.md` — 16 structured methodology files across 5 pillars + 3 automation skills
+- **MCP Server**: `crewpilot-engine/` (CrewPilot MCP server) — TypeScript MCP server with 55 tools across 8 modules + config
+
+## How to Use
+
+Type `@crewpilot` in GitHub Copilot Chat. The agent will ask for a session role (Build, Review, Plan, Design, or Just Ask), then route your requests to the appropriate skill.
+
+## Key Conventions
+
+- **Conventional commits**: `type(scope): message`
+- **Human gates**: Autopilot always pauses for approval at critical points
+- **Branch protection**: Never commit directly to `main`/`master`/`release/*`
+- **Progressive disclosure**: Summaries first, details on request
+- **Confidence gating**: Findings below threshold (default 7/10) are suppressed
+
+## Configuration
+
+`.github/crewpilot.config.json` controls thresholds, pillar toggles, and per-skill overrides. See `crewpilot_config_get` tool.
+
+## Architecture
+
+```
+User → @crewpilot (router) → SKILL.md (methodology) → MCP tools (execution)
+                                                      ↓
+                                          SQLite (knowledge + workflows)
+                                          gh CLI (GitHub Issues/PRs)
+```
+
+For full details, see the [README](../README.md) or the [agent definition](agents/crewpilot.md).

package/prompts/{catalyst.config.json → crewpilot.config.json}

@@ -1,72 +1,72 @@
-{
-  "version": "1.3.0",
-  "platform": "CrewPilot — Your AI Engineering Crew",
-  "global": {
-    "confidence_threshold": 7,
-    "max_findings": 20,
-    "output_style": "concise",
-    "auto_chain": true
-  },
-  "board": {
-    "provider": "github",
-    "github": {
-      "repo": "",
-      "auto_detect": true
-    },
-    "azure": {
-      "org": "performanceagent",
-      "project": "Catalyst"
-    },
-    "sync_on_commit": true
-  },
-  "worker": {
-    "enabled": true,
-    "max_retries": 3,
-    "human_gates": ["approve-plan", "approve-pr", "approve-merge"],
-    "auto_assign_label": "digital-worker"
-  },
-  "notifications": {
-    "channel": "email",
-    "email_recipients": []
-  },
-  "pillars": {
-    "strategize": {
-      "enabled": true,
-      "skills": {
-        "solution-design": { "enabled": true, "max_options": 4 },
-        "architecture-planner": { "enabled": true, "require_adr": true }
-      }
-    },
-    "assure": {
-      "enabled": true,
-      "skills": {
-        "code-quality": { "enabled": true, "severity_floor": "medium" },
-        "vulnerability-scan": { "enabled": true, "owasp_top_10": true, "cwe_top_25": true },
-        "pr-intelligence": { "enabled": true, "auto_summarize": true }
-      }
-    },
-    "engineer": {
-      "enabled": true,
-      "skills": {
-        "feature-builder": { "enabled": true, "scaffold_tests": true },
-        "test-first": { "enabled": true, "enforcement": "strict", "min_coverage": 80 },
-        "root-cause-analysis": { "enabled": true, "max_attempts": 5 }
-      }
-    },
-    "deliver": {
-      "enabled": true,
-      "skills": {
-        "change-management": { "enabled": true, "commit_format": "conventional" },
-        "doc-governance": { "enabled": true, "drift_detection": true },
-        "deploy-guard": { "enabled": true, "phase_gates": "strict" }
-      }
-    },
-    "insights": {
-      "enabled": true,
-      "skills": {
-        "pattern-detection": { "enabled": true, "scan_depth": "full" },
-        "knowledge-base": { "enabled": true, "retention_days": 90 }
-      }
-    }
-  }
-}
+{
+  "version": "1.3.0",
+  "platform": "CrewPilot — Your AI Engineering Crew",
+  "global": {
+    "confidence_threshold": 7,
+    "max_findings": 20,
+    "output_style": "concise",
+    "auto_chain": true
+  },
+  "board": {
+    "provider": "github",
+    "github": {
+      "repo": "",
+      "auto_detect": true
+    },
+    "azure": {
+      "org": "performanceagent",
+      "project": "CrewPilot"
+    },
+    "sync_on_commit": true
+  },
+  "worker": {
+    "enabled": true,
+    "max_retries": 3,
+    "human_gates": ["approve-plan", "approve-pr", "approve-merge"],
+    "auto_assign_label": "digital-worker"
+  },
+  "notifications": {
+    "channel": "email",
+    "email_recipients": []
+  },
+  "pillars": {
+    "strategize": {
+      "enabled": true,
+      "skills": {
+        "solution-design": { "enabled": true, "max_options": 4 },
+        "architecture-planner": { "enabled": true, "require_adr": true }
+      }
+    },
+    "assure": {
+      "enabled": true,
+      "skills": {
+        "code-quality": { "enabled": true, "severity_floor": "medium" },
+        "vulnerability-scan": { "enabled": true, "owasp_top_10": true, "cwe_top_25": true },
+        "pr-intelligence": { "enabled": true, "auto_summarize": true }
+      }
+    },
+    "engineer": {
+      "enabled": true,
+      "skills": {
+        "feature-builder": { "enabled": true, "scaffold_tests": true },
+        "test-first": { "enabled": true, "enforcement": "strict", "min_coverage": 80 },
+        "root-cause-analysis": { "enabled": true, "max_attempts": 5 }
+      }
+    },
+    "deliver": {
+      "enabled": true,
+      "skills": {
+        "change-management": { "enabled": true, "commit_format": "conventional" },
+        "doc-governance": { "enabled": true, "drift_detection": true },
+        "deploy-guard": { "enabled": true, "phase_gates": "strict" }
+      }
+    },
+    "insights": {
+      "enabled": true,
+      "skills": {
+        "pattern-detection": { "enabled": true, "scan_depth": "full" },
+        "knowledge-base": { "enabled": true, "retention_days": 90 }
+      }
+    }
+  }
+}

package/prompts/skills/assure-code-quality/SKILL.md

@@ -1,112 +1,112 @@
-# Code Quality
-
-> **Pillar**: Assure | **ID**: `assure-code-quality`
-
-## Purpose
-
-Multi-pass code review that identifies quality issues across correctness, maintainability, performance, and readability. Goes beyond linting — analyzes design intent and structural health.
-
-## Activation Triggers
-
-- "review this code", "code quality check", "refactor suggestions", "clean code"
-- "what's wrong with this", "improve this", "code smell"
-- When any file is shared for review
-
-## Methodology
-
-### Process Flow
-
-```dot
-digraph code_quality {
-    rankdir=LR;
-    node [shape=box];
-
-    correctness [label="Pass 1\nCorrectness"];
-    maintainability [label="Pass 2\nMaintainability"];
-    performance [label="Pass 3\nPerformance"];
-    readability [label="Pass 4\nReadability"];
-    synthesis [label="Synthesis\nRank & Filter", shape=doublecircle];
-
-    correctness -> maintainability;
-    maintainability -> performance;
-    performance -> readability;
-    readability -> synthesis;
-}
-```
-
-### Pass 1 — Correctness
-1. Identify logic errors, off-by-one, null/undefined risks, race conditions
-2. Check edge cases: empty inputs, boundary values, error paths
-3. Verify resource cleanup (connections, file handles, subscriptions)
-4. Confidence-gate: only report findings ≥ threshold
-
-### Pass 2 — Maintainability
-1. Check function/class length — flag functions > 30 lines, classes > 300 lines
-2. Identify code duplication (exact and near-duplicate)
-3. Evaluate naming clarity — do names reveal intent?
-4. Check coupling: does this code depend on internal details of other modules?
-5. Apply SOLID principles where applicable (but don't lecture)
-
-### Pass 3 — Performance
-1. Identify O(n²) or worse patterns in hot paths
-2. Flag unnecessary allocations in loops
-3. Check for N+1 query patterns (if data access is involved)
-4. Look for missing caching opportunities on repeated computations
-5. Identify blocking calls that could be async
-
-### Pass 4 — Readability
-1. Assess cognitive complexity (nesting depth, boolean chains)
-2. Check for magic numbers/strings
-3. Verify consistent style within the file
-4. Evaluate comment quality — helpful vs. noise vs. missing
-
-### Synthesis
-1. Rank all findings by severity: `critical > high > medium > low`
-2. Filter by `severity_floor` from config
-3. Group by file/function
-4. Provide specific fix suggestions with code snippets
-
-## Tools Required
-
-- `codebase` — Read files and understand structure
-- `catalyst_metrics_complexity` — Get cyclomatic/cognitive complexity scores
-- `catalyst_metrics_coverage` — Check test coverage for reviewed code
-
-## Output Format
-
-```
-## [Catalyst → Code Quality]
-
-### Summary
-{N} findings across {files}: {critical} critical, {high} high, {medium} medium
-
-### Findings
-
-#### [{severity}] {title}
-**File**: {path}:{line}
-**Issue**: {description}
-**Fix**:
-\`\`\`{lang}
-{suggested fix}
-\`\`\`
-**Confidence**: {N}/10
-
----
-(repeat per finding)
-
-### Recommendations
-{top 3 structural improvements, if any}
-```
-
-## Chains To
-
-- `test-first` — Write tests for areas with correctness concerns
-- `vulnerability-scan` — If security-adjacent patterns are detected
-- `change-management` — When fixes are ready to commit
-
-## Anti-Patterns
-
-- Do NOT report style preferences as quality issues
-- Do NOT suggest heroic refactoring for stable, working code
-- Do NOT report findings below the configured severity floor
-- Do NOT rewrite the user's code in a different paradigm unless asked
+# Code Quality
+
+> **Pillar**: Assure | **ID**: `assure-code-quality`
+
+## Purpose
+
+Multi-pass code review that identifies quality issues across correctness, maintainability, performance, and readability. Goes beyond linting — analyzes design intent and structural health.
+
+## Activation Triggers
+
+- "review this code", "code quality check", "refactor suggestions", "clean code"
+- "what's wrong with this", "improve this", "code smell"
+- When any file is shared for review
+
+## Methodology
+
+### Process Flow
+
+```dot
+digraph code_quality {
+    rankdir=LR;
+    node [shape=box];
+
+    correctness [label="Pass 1\nCorrectness"];
+    maintainability [label="Pass 2\nMaintainability"];
+    performance [label="Pass 3\nPerformance"];
+    readability [label="Pass 4\nReadability"];
+    synthesis [label="Synthesis\nRank & Filter", shape=doublecircle];
+
+    correctness -> maintainability;
+    maintainability -> performance;
+    performance -> readability;
+    readability -> synthesis;
+}
+```
+
+### Pass 1 — Correctness
+1. Identify logic errors, off-by-one, null/undefined risks, race conditions
+2. Check edge cases: empty inputs, boundary values, error paths
+3. Verify resource cleanup (connections, file handles, subscriptions)
+4. Confidence-gate: only report findings ≥ threshold
+
+### Pass 2 — Maintainability
+1. Check function/class length — flag functions > 30 lines, classes > 300 lines
+2. Identify code duplication (exact and near-duplicate)
+3. Evaluate naming clarity — do names reveal intent?
+4. Check coupling: does this code depend on internal details of other modules?
+5. Apply SOLID principles where applicable (but don't lecture)
+
+### Pass 3 — Performance
+1. Identify O(n²) or worse patterns in hot paths
+2. Flag unnecessary allocations in loops
+3. Check for N+1 query patterns (if data access is involved)
+4. Look for missing caching opportunities on repeated computations
+5. Identify blocking calls that could be async
+
+### Pass 4 — Readability
+1. Assess cognitive complexity (nesting depth, boolean chains)
+2. Check for magic numbers/strings
+3. Verify consistent style within the file
+4. Evaluate comment quality — helpful vs. noise vs. missing
+
+### Synthesis
+1. Rank all findings by severity: `critical > high > medium > low`
+2. Filter by `severity_floor` from config
+3. Group by file/function
+4. Provide specific fix suggestions with code snippets
+
+## Tools Required
+
+- `codebase` — Read files and understand structure
+- `crewpilot_metrics_complexity` — Get cyclomatic/cognitive complexity scores
+- `crewpilot_metrics_coverage` — Check test coverage for reviewed code
+
+## Output Format
+
+```
+## [CrewPilot → Code Quality]
+
+### Summary
+{N} findings across {files}: {critical} critical, {high} high, {medium} medium
+
+### Findings
+
+#### [{severity}] {title}
+**File**: {path}:{line}
+**Issue**: {description}
+**Fix**:
+\`\`\`{lang}
+{suggested fix}
+\`\`\`
+**Confidence**: {N}/10
+
+---
+(repeat per finding)
+
+### Recommendations
+{top 3 structural improvements, if any}
+```
+
+## Chains To
+
+- `test-first` — Write tests for areas with correctness concerns
+- `vulnerability-scan` — If security-adjacent patterns are detected
+- `change-management` — When fixes are ready to commit
+
+## Anti-Patterns
+
+- Do NOT report style preferences as quality issues
+- Do NOT suggest heroic refactoring for stable, working code
+- Do NOT report findings below the configured severity floor
+- Do NOT rewrite the user's code in a different paradigm unless asked