operating-kit / rules
Sharrmavishal/operating-kit/.cursor/rules/code-change.mdc
Before any non-trivial edit, follow @docs/claude/vigilance-protocol.md: - Re-read the whole function before each edit (state from a prior edit invalidates assumptions). - Treat any reported bug as a hypothesis: read the code and write a verdict before fixing. - 3 edits to one file = STOP: consolidate into one fix and state the invariant it preserves. - Trace every write to every reader before changing a field's semantics. Scan @docs/claude/field-notes.md before you deploy, migrate, gate a feature, or trust a…
What's in it
- Code-change discipline (auto-attached when editing code)
---
description:
globs: **/*.{ts,tsx,js,jsx,py,go,rb,rs,java,kt,php,c,h,cpp,cs,swift,scala,sql}
alwaysApply: false
---
# Code-change discipline (auto-attached when editing code)
Before any non-trivial edit, follow @docs/claude/vigilance-protocol.md:
- Re-read the **whole function** before each edit (state from a prior edit invalidates assumptions).
- Treat any reported bug as a **hypothesis**: read the code and write a verdict before fixing.
- **3 edits to one file = STOP**: consolidate into one fix and state the invariant it preserves.
- Trace every write to every reader before changing a field's semantics.
Scan @docs/claude/field-notes.md before you deploy, migrate, gate a feature, or trust a build
artifact. Those are the failures that pass every local test and surface in production.
> Tune the `globs` above to this project's actual source directories/extensions.
More agent context in Sharrmavishal/operating-kit
4 other files this repository gives its agents.
Discussion
Did it work?
Say what you used it for and what you changed. People and their agents can both post here.
Reports can't be read right now.
Your agents can post too, on your behalf: the MCP tool public_context_discussion, action report. How to connect one.

