night-watch-fix

Reproduce software incidents, implement fixes, validate changes, and prepare pull requests.

1|1|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/dapperdivers/roundtable-arsenal --skill night-watch-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: night-watch-fix
Source: https://github.com/dapperdivers/roundtable-arsenal/tree/main/coding/night-watch-fix
Command: npx skills add https://github.com/dapperdivers/roundtable-arsenal --skill night-watch-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps coding agents handle Night Watch incident missions by turning reported fingerprints and evidence into verified fixes, regression checks, and reviewable pull requests.

Core Features & Use Cases

  • Incident Resolution Workflow: Guides agents through reproduction, root-cause analysis, minimal fixes, testing, and PR preparation for dispatched incidents.
  • Repository-Aware Validation: Applies repo-specific verification steps and protects sensitive paths during remediation work.
  • Use Case: When a watchman reports a fingerprinted production issue, use this Skill to investigate the failure, implement the smallest correct change, and open a PR with a structured incident summary.

Quick Start

Use the night-watch-fix skill to resolve the incident mission described in the provided Night Watch briefing and prepare a pull request.

Frequently Asked Questions about night-watch-fix

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

FAQPage Schema
How do I resolve production incidents and prepare safe code fixes?

To resolve production incidents, you reproduce the reported failure, implement minimal code remediation, validate changes through repository-specific testing, and prepare a structured pull request for controlled deployment.

What is the incident response workflow for fixing dispatched bugs in a repository?

The incident response workflow for fixing bugs involves reproducing the failure from evidence, performing root-cause analysis, applying the smallest correct change, running regression checks, and opening a pull request with an incident summary.

How do I ensure bug fixing does not break protected paths during code remediation?

To ensure bug fixing does not break protected paths, code remediation applies repository-aware validation steps and maintains strict branch discipline to prevent unauthorized changes to sensitive code sections.

Can I use a single workflow for incident remediation across multiple repositories?

Yes, you can use a unified incident remediation workflow across multiple repositories by applying standardized verification processes, branch discipline, and structured PR reporting to handle dispatched missions consistently.

What is the best way to format a pull request for an incident response?

The best way to format a pull request for incident response is to include a structured incident summary that details the reproduced failure, the applied fix, and the validation steps performed during code remediation.