Use this skill whenever code or documentation changes are about to be committed to git. Triggers include "commit this", "save progress", completion of a feature or fix, or recognition that uncommitted changes should land as a logical unit. Always use before running `git commit` on this repository — the git identity check and Conventional Commits contract here are strict, and past identity contamination has required force-push remediation.
Use this skill when a session's decisions are final and either the work is complete or the session has produced stable rules that should be promoted. Triggers include "freeze this", "lock it in", "we're done with this decision", "ratify these rules", or recognition that all open questions are answered and the implementation plan has been executed or consciously parked. Always use when a session transitions from in-progress to a stable decision record; this is what keeps the conventions catalogue growing and the sessions index free of stale "in-progress" entries.
Use this skill whenever a new version of a package in this monorepo needs to be published to npm. Triggers include "release rc", "cut a patch", "publish <pkg>", "bump sdk", or any phrasing asking for a new version of `@namzu/sdk`, `@namzu/computer-use`, or another publishable workspace. Always use this skill rather than hand-editing `package.json#version` — Changesets owns version state and the Changesets-driven workflow is the only sanctioned publish path.
Use this skill before making any non-trivial code change, architectural decision, or refactor to ensure compliance with ratified project rules. Triggers include writing new code for a feature, refactoring existing code shape, adding a new package or entity, touching public API, or reviewing a PR for compliance. Always use before a non-trivial change. Skip only for typo fixes and documentation-only edits. Silent deviation from a ratified rule is forbidden; this skill is the way to avoid it.
Use this skill whenever a code change alters anything documented in `docs/` — public API, CLI behavior, wire schema, exported types, configuration, or user-facing workflow. Triggers include freezing a session whose decisions touched the public surface, merging a feature that adds or renames an exported symbol, changing CLI flag semantics, or user phrasing like "update the docs", "docs are stale", "sync documentation". Always use when the published surface changes — out-of-date docs are the most common and most costly drift in this repo.
Use this skill after drafting any non-trivial plan, design, or implementation approach to obtain an adversarial second opinion from Codex. Triggers include "get a second opinion", "check this plan", "what did I miss", completion of a `design.md` or `implementation-plan.md`, or before executing a migration, refactor, or public-surface change. Always use on non-trivial work — skip only for typo fixes and one-line edits. The value of this skill is push-back, not confirmation; generic praise returned by Codex is discarded.
Use this skill whenever the user resumes existing design, architectural, or planning work, or whenever a fresh agent takes over and must locate prior context. Triggers include references to "last time", "where we left off", "the <slug> session", "continue the refactor", any mention of a session ID like "ses_001", or ambiguity about what work is in flight. Always use this before starting new work that might already have an open session — creating a duplicate session loses context and fragments decisions.
Use this skill whenever the user begins new non-trivial design, architectural, refactoring, investigation, or planning work that deserves a decision log. Triggers include requests to design a feature, plan a refactor, propose an approach, explore options, or work through any change that spans multiple decisions. Always prefer opening a session over working in-place on work that will produce durable decisions or span more than one exchange. Do NOT use for trivial fixes such as typos or one-line bug fixes.