kc-nightwatch-report

Summarize kc-nightwatch run logs and review proposal branches with diffs.

3|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/iamcxa/kc-claude-plugins --skill kc-nightwatch-report
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kc-nightwatch-report
Source: https://github.com/iamcxa/kc-claude-plugins/tree/main/kc-nightwatch/skills/kc-nightwatch-report
Command: npx skills add https://github.com/iamcxa/kc-claude-plugins --skill kc-nightwatch-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a single command to understand recent kc-nightwatch activity, inspect detailed run traces, compare recent runs, and review or act on pending proposal and fix branches so maintainers don't miss regressions or unattended improvement suggestions.

Core Features & Use Cases

  • Status Summary: Quickly surface last run metadata, total runs, and recent improvement entries from the improvement log.
  • Trace & Compare: Show a human-readable execution trace of the last run or compare the last N runs to detect trends and recurring signals.
  • Interactive Review Queue: Discover kc-nightwatch proposal and fix branches across target repos, show diffs and PROPOSAL.md contents, and provide accept/defer/reject workflows that merge or delete branches and close PRs.
  • Use Case: A plugin maintainer runs the report to see that an e2e pipeline produced repeated signals, inspects the trace, reviews a proposed fix branch, and merges the accepted fix into main.

Quick Start

Run /kc-nightwatch-report --review to interactively inspect pending proposal branches and accept, defer, or reject them.

Frequently Asked Questions about kc-nightwatch-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review pending git branches from automated CI runs?▼

You can review pending git branches from automated CI runs by executing an interactive review queue that discovers kc-nightwatch proposal and fix branches, shows diffs and PROPOSAL.md contents, and provides accept, defer, or reject workflows to merge or delete branches.

How do I compare recent nightwatch run traces to detect recurring regression signals?▼

You can compare recent nightwatch run traces by parsing local run logs to show a human-readable execution trace of the last run or compare the last N runs side-by-side to detect trends and recurring signals across your CI pipelines.

What is the best way to summarize nightwatch automation status across multiple repositories?▼

Summarizing nightwatch automation status across multiple repositories involves reading local kc-nightwatch configuration and run logs to surface last run metadata, total runs, and recent improvement entries from the improvement log in a single consolidated view.

Can I merge or reject proposal branches directly from a nightwatch report?▼

Yes, you can merge or reject proposal branches directly from a nightwatch report by using the interactive review queue, which provides accept, defer, and reject actions that merge accepted fixes into main or delete rejected branches and close associated PRs.

Do I need external dependencies to inspect nightwatch run logs and improvement logs?▼

No external dependencies are required to inspect nightwatch run logs and improvement logs, as the reporting tool reads local kc-nightwatch configuration, parses run logs, and enumerates git branches matching kc-nightwatch/* directly within your existing environment.