sachinshelke

development-discipline

Use this skill before ANY code-writing tool call (Edit, Write, NotebookEdit) on this project. Triggers on phrases like "implement", "fix bug", "add feature", "refactor", "create function", "modify file", or whenever the user asks for a code change. Forces a 4-step CONTEXT → PURPOSE → REASON → CODE sequence with explicit checks at each step. Refuses to write code until all four are answered. Also covers reuse-first, single-source- of-truth, blast-radius-aware, minimal-diff, and test-as-evidence sub-rules.

epistemic-honesty

Use this skill whenever you're about to (1) make a definitive claim like "this works", "tests pass", "ready to ship", "fixed", "done"; or (2) propose a solution to a problem; or (3) diagnose a bug or issue. Forces explicit confidence calibration with inline evidence, surfaces what you don't know, and demands a first-contact-empathy walkthrough before declaring any work complete. Refuses to declare anything "done" without verification.

foolproof-product

Use this skill on ANY code change in codevira's product surface (mcp_server/, indexer/). Triggers on Edit/Write to product code, on phrases like "fix bug", "add feature", "handle error", or any modification to commands the end-user runs. Enforces 10 product- reliability principles: no silent failures, atomic state mutations, defensive parsing, bounded resources, predictable detection, reversible operations, helpful error messages, graceful degradation, observability, self-diagnosis. Refuses to ship code that violates any of them.

open-source-quality

Use this skill before committing, pushing, or opening a PR. Triggers on phrases like "commit", "git commit", "push", "open PR", "create pull request", "finalize this change". Enforces conventional commit messages, atomic commits, code style (ruff/mypy), public-API docstrings, actionable error messages, changelog discipline, and backwards-compat warnings. Refuses to declare commits ready without passing these checks.

release-readiness

Use this skill whenever the conversation mentions releasing, shipping, publishing, promoting to PyPI, "ship it", "release X.Y.Z", "ready to release", "let's publish", or any phrase suggesting moving codevira to production. Walks the 5-gate release gauntlet (G1-G5) and refuses to proceed without evidence at every gate. Never produces release commands without confirming the gauntlet passed.