kc-nightwatch

Run nightly plugin repository validation and signal harvesting with automated fixes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

kc-nightwatch automates nightly quality monitoring and improvement for a plugin ecosystem by harvesting signals, validating structure, and proposing or applying fixes so maintainers don't miss regressions or repetitive maintenance work.

Core Features & Use Cases

  • Forge validation & auto-fix: Run structural checks with kc-plugin-forge, create limited auto-fix branches, and re-validate to reduce trivial FAIL items.
  • Signal harvesting: Aggregate signals from journal entries, Sentry, git stats, and E2E reports, deduplicate across sources, and prioritize by confidence and cooldown rules.
  • Feedback loop & reporting: Collect PR/Linear/Slack feedback, compute reject rates, adapt thresholds, and produce daily Slack reports and Linear issues or PR proposals.
  • Use Case: Nightly run scans a plugin repo, auto-fixes small schema issues, files proposals for behavioral changes, and generates a morning report linking dispatched PRs and issues.

Quick Start

Run kc-nightwatch to perform a nightly validation, harvest signals, and generate improvement proposals for configured targets.

Frequently Asked Questions about kc-nightwatch

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

FAQPage Schema
How do I automate nightly plugin validation and auto-fixing?

Nightly plugin validation automates structural checks using forge validation, creates limited auto-fix branches for small schema issues, and re-validates to reduce trivial failures. It harvests signals from Sentry, git stats, and E2E reports to propose or apply fixes.

What is signal harvesting from Sentry and E2E reports for plugin maintenance?

Signal harvesting aggregates journal entries, Sentry errors, git stats, and E2E reports to monitor plugin quality. It deduplicates issues across sources and prioritizes them using confidence and cooldown rules to prevent repetitive maintenance work.

Can I integrate automated self-repair with Linear and Slack reporting?

Automated self-repair integrates with Linear and Slack by collecting PR feedback, computing reject rates, and adapting thresholds. It coordinates creating Linear issues, dispatching PR proposals, and generating daily Slack reports for maintainers.

How does cooldown-based deduplication work for plugin issue proposals?

Cooldown-based deduplication prevents repeated fixes for the same plugin issue by tracking signal confidence and timestamps. It ensures only new or unresolved regressions generate PR proposals or Linear issues during nightly runs.

What are the safety limits for edit-only auto-fixes in plugin repositories?

Edit-only auto-fixes enforce configurable safety limits that restrict automated changes to structural schema corrections. This prevents unintended behavioral modifications while allowing the system to safely reduce trivial validation failures.

Does kc-nightwatch work with kc-plugin-forge for structural validation?

kc-nightwatch works with kc-plugin-forge to run structural checks across plugin and product targets. It leverages forge validation results to detect structural and behavioral issues, then applies limited auto-fixes and re-validates the repository.