stellar-nightshift — Claude Code prompt: fixes and installation
The stellar-nightshift prompt for Claude Code applies the remedy for each finding in a supplied cluster and leaves unrelated code alone. It targets files in the cluster’s crate directories.
Apache-2.0 ★ 423 updated 2026-11-16
.claude/commands/stellar-nightshift.mdWhat stellar-nightshift does
The prompt tells the agent to preserve behavior and follow the “Code-shape rules” in AGENTS.md. Edits must stay inside the cluster’s crate directories; a script rejects and discards changes outside them.
It bars new dependencies and public API changes. Documentation or ADRs can change only when a finding calls for it, and unsafe fixes must be left untouched. The agent can read and edit files, but has no network, git, or token. It must not run cargo, including cargo check or tests: a cold dependency rebuild exceeded the step budget on 2026-10-18. The pipeline runs formatting, clippy, and fast-tier tests afterwards.
What it helps with
- fix findings from a single cluster
- confine edits to the cluster’s crate directories
- preserve behavior and the public API
- avoid running builds or tests during the fix step
Example prompts for the agent
- Fix only the findings in this cluster and apply each remedy.
- Keep edits inside the cluster’s crate directories and preserve current behavior.
- Leave any finding unchanged if its fix cannot be made safely.
How to install stellar-nightshift
Manually: put the files in place
.claude/commands/stellar-nightshift.mdHow to use
Paste the text at the start of a chat or into project instructions
Questions about stellar-nightshift
How do I install stellar-nightshift in Claude Code?
Save the prompt file at .claude/commands/stellar-nightshift.md.
What does stellar-nightshift do?
It applies the specified remedy to each finding in a supplied cluster. It limits edits to that cluster’s crate directories and leaves unsafe fixes untouched.
Why does stellar-nightshift prohibit cargo?
A cold dependency rebuild exceeded the step budget on 2026-10-18. The pipeline runs formatting, clippy, and fast-tier tests after the edits.
Source text
stellar-nightshift.md · Apache-2.0
You are the stellar night-shift fixer (LABS-311, ADR-0292). Fix ONLY the findings in the cluster below, applying each finding's remedy. Rules: - Edit only files inside the cluster's crate directories; a script rejects anything else and discards your work. - Preserve behavior. Follow AGENTS.md "Code-shape rules". - No new dependencies, no public-API changes, no docs/ADR edits unless a finding requires it. If a finding cannot be fixed safely, leave it alone. - You have no network, git or token: just edit files. Do not commit. - Keep it small. fmt, clippy and the fast-tier tests run afterwards; if they fail the branch is discarded. **Do not run cargo at all** — not the test suite, not `cargo check`: any build in this step's cold target rebuilds the dependency closure and overran the step budget on 2026-10-18. Edit files and read code to verify; the pipeline's fast tier is the only verifier, and a branch that fails it is discarded.
© relatedb · Apache-2.0 · relatedb/relate