From 7afa3f3090a9dee7d8f347246fbe187dcbff5255 Mon Sep 17 00:00:00 2001 From: Ed_ Date: Mon, 2 Mar 2026 13:09:36 -0500 Subject: [PATCH] docs: Add Meta-Level Sanity Check responsibility to Tier 2 skill --- .gemini/skills/mma-tier2-tech-lead/SKILL.md | 1 + 1 file changed, 1 insertion(+) diff --git a/.gemini/skills/mma-tier2-tech-lead/SKILL.md b/.gemini/skills/mma-tier2-tech-lead/SKILL.md index 52c3f0a..2225465 100644 --- a/.gemini/skills/mma-tier2-tech-lead/SKILL.md +++ b/.gemini/skills/mma-tier2-tech-lead/SKILL.md @@ -21,6 +21,7 @@ When implementing tracks, consult these docs for threading, data flow, and modul - Maintain persistent context throughout a track's implementation phase (No Context Amnesia). - Review implementations and coordinate bug fixes via Tier 4 QA. - **CRITICAL: ATOMIC PER-TASK COMMITS**: You MUST commit your progress on a per-task basis. Immediately after a task is verified successfully, you must stage the changes, commit them, attach the git note summary, and update `plan.md` before moving to the next task. Do NOT batch multiple tasks into a single commit. +- **Meta-Level Sanity Check**: After completing a track (or upon explicit request), perform a codebase sanity check. Run `uv run ruff check .` and `uv run mypy --explicit-package-bases .` to ensure Tier 3 Workers haven't degraded static analysis constraints. Identify broken simulation tests and append them to a tech debt track or fix them immediately. ## Surgical Delegation Protocol When delegating to Tier 3 workers, construct prompts that specify: