| name | nightward |
| description | Use Nightward to audit local AI agent/devtool config, inspect MCP risk, and generate dry-run backup or schedule plans without leaking secrets. |
Nightward
Use this skill when a task asks to inspect local AI agent configs, MCP servers, dotfiles backup safety, or scheduled config scans with the nightward CLI.
Safe Order
-
Verify the command exists:
command -v nightward || go run ./cmd/nightward --help
-
Run a read-only health check:
nightward doctor --json
-
Run a redacted scan:
nightward scan --json
-
Generate a dry-run backup plan:
nightward plan backup --json
-
Preview scheduling before installing anything:
nightward schedule install --preset nightly --dry-run
Do Not
- Do not run
schedule install or schedule remove without explicit user approval.
- Do not copy files from scan output manually; use the backup plan classifications.
- Do not sync
secret-auth, runtime-cache, or app-owned items into dotfiles.
- Do not assume MCP findings are false positives; review the command, env keys, and local paths first.
Notes
Nightward v1 is local-only and read-mostly. Scan and plan commands do not mutate user config. The only write paths are explicit schedule install/remove commands.
Repository Commits
Nightward requires DCO on every non-merge commit. Use git commit -s or git commit --signoff for all Nightward commits, while preserving the normal local signing setup.
