kc-nightwatch

Scan E2E test reports for failure trends, coverage gaps, and stale mappings. Returns structured YAML with confidence-rated findings. Dispatched by kc-nightwatch orchestrator during Phase 2 for targets with `e2e-reports` in sources. <example> Context: kc-nightwatch orchestrator needs E2E signals for my-app user: "Scan E2E reports for my-app. Path: ~/Project/my-app. Keywords: [checkout, order]. North star: Checkout flow completes with zero friction. Proxy signals: e2e-coverage." assistant: "Scanning E2E report directories for failure trends and coverage gaps." <commentary>Scans .claude/e2e/ and e2e-reports/ for test results and mapping staleness.</commentary> </example> <example> Context: kc-nightwatch orchestrator scans a project with no E2E infrastructure user: "Scan E2E reports for my-service. Path: ~/Project/my-service. Keywords: [api, validation]. North star: API validation with zero config. Proxy signals: validation-coverage." assistant: "No e2e-reports/ or .claude/e2e/ directories found — returning empty signals." <commentary>Graceful with missing dirs: projects without E2E infrastructure get empty signals, not errors.</commentary> </example>

Analyze git history for churn hotspots and long-untouched code areas. Returns structured YAML with confidence-rated findings. Dispatched by kc-nightwatch orchestrator during Phase 2 for targets with `git-stats` in sources. <example> Context: kc-nightwatch orchestrator needs git stats for my-app user: "Scan git stats for my-app. Path: ~/Project/my-app. Keywords: [checkout, order]. North star: Checkout flow completes with zero friction. Proxy signals: checkout-friction." assistant: "Analyzing git log for high-churn hotspots and stale code areas." <commentary>Uses git log --since for commit frequency analysis by directory.</commentary> </example> <example> Context: kc-nightwatch orchestrator scans a plugin repo (not a product) for git churn user: "Scan git stats for kc-pr-flow. Path: ~/Project/my-workspace/kc-pr-flow. Keywords: [PR, review, create-pr]. North star: PR lifecycle from creation to review response. Proxy signals: skill-coverage, review-friction." assistant: "Analyzing git log for high-churn skill files and stale references." <commentary>Git scanner works on any git repo, including plugin repos — not limited to product targets.</commentary> </example>

Scan Sentry for production error signals — new issues, error spikes, regressions. Returns structured YAML with confidence-rated findings. Dispatched by kc-nightwatch orchestrator during Phase 2 for targets with `sentry` in sources. <example> Context: kc-nightwatch orchestrator needs Sentry signals for my-app user: "Scan Sentry for my-app. Project: my-app-web. Keywords: [checkout, order, payment]. North star: Checkout flow completes with zero manual intervention. Proxy signals: checkout-friction, error-rate, e2e-coverage." assistant: "Searching Sentry project my-app-web for production error signals." <commentary>Dispatched for targets with sentry in sources and sentry_project configured.</commentary> </example> <example> Context: kc-nightwatch orchestrator needs Sentry signals but MCP tools are unavailable user: "Scan Sentry for my-service. Project: my-service-api. Keywords: [api, auth, webhook]. North star: API reliability above 99.9%. Proxy signals: error-rate." assistant: "Sentry MCP tools not available — returning empty signals with warning." <commentary>Graceful degradation: when Sentry MCP tools fail, return empty YAML with warning instead of erroring.</commentary> </example>

Search journal, episodic memory, and MEMORY.md for plugin improvement signals aligned with north star goals. Returns structured YAML with confidence-rated findings. Dispatched by kc-nightwatch orchestrator during Phase 2 (Signal Harvest). <example> Context: kc-nightwatch orchestrator is running Phase 2 and needs improvement signals for kc-pr-flow user: "Harvest signals for kc-pr-flow. Keywords: [PR, review, pr-flow, create-pr, code review]. North star: PR lifecycle from creation to review response. Proxy signals: skill-coverage, review-friction. Plugin path: ~/Project/my-workspace/kc-pr-flow. Repo: my-plugins." assistant: "Searching journal, episodic memory, and MEMORY.md for kc-pr-flow improvement signals." <commentary>Phase 2 dispatches one harvester per plugin with keywords and north star context from nightwatch-targets.yaml.</commentary> </example> <example> Context: kc-nightwatch orchestrator needs signals for e2e-pipeline (different repo) user: "Harvest signals for e2e-pipeline. Keywords: [e2e, browser test, mapping, walkthrough, flow, selector]. North star: Browser E2E testing is fully automated. Proxy signals: mapping-freshness, flow-coverage, pipeline-friction. Plugin path: ~/Project/my-workspace/e2e-pipeline. Repo: my-plugins." assistant: "Searching all three sources for e2e-pipeline improvement signals." <commentary>Harvester works the same regardless of which repo the plugin is in — repo field is passed through to output.</commentary> </example>

Use when setting up, configuring, or managing kc-nightwatch scheduling and settings. Triggered by '/kc-nightwatch-config', or when user asks to schedule nightwatch, change cron time, configure Slack channel, or check what plugins are monitored.

Use when checking nightwatch status, viewing last run results, reviewing improvement history, or reviewing pending proposals. Triggered by '/kc-nightwatch-report', '/kc-nightwatch-report --last', '/kc-nightwatch-report --review', or asking about nightwatch activity.

Use when running nightly plugin improvement cycle — forge validation, signal harvesting, north-star gap analysis, auto-fix and proposal generation. Triggered by cron or manual invocation.