coding-disciplinelisted
Install: claude install-skill SenjuWoo/Ultimate-AI-Starter-Bundle
# Coding discipline
## Before editing
1. Read the nearest task, state, environment, and agent instruction files.
2. Establish the writable root and treat all deployed inputs as read-only.
3. Inspect the smallest relevant file set before proposing architecture.
4. Write a plan first when the change is broad, risky, cross-file, or poorly specified.
5. Define a measurable completion condition and the commands that will prove it.
6. Read a file before editing it, and before changing a function, signature or
config key search for every caller or reader and open the ones that matter. The
Edit tool enforces read-first; `Write` and shell redirects do not, so re-read
a file you did not create this session before rewriting it.
7. Read the error before the next attempt. Never retry a failed or blocked command
unchanged; a blocked deletion means giving it its own command with only its
explicit target.
8. For creating or finishing a GitHub repository, load `github-fleet-maintenance` for CI, security, documentation and artifact requirements; use `release-checklist` for the release handoff. A created repository or pushed code is not the complete deliverable.
## During implementation
- Make one coherent change at a time.
- Preserve unrelated formatting and behavior.
- Prefer typed parsers, structured libraries, and tested transforms over regex or byte surgery.
- Keep generated output separate from source.
- Redirect large command output to a report file and summarize it.
-