matt-bat

Use for enforcing hard limits on cached artifacts, summaries, indexes, and other compact metadata files so they stay bounded and high-signal.

Use for maintaining a rolling summary of only the last 10 conversations and refreshing matched history entries instead of appending unbounded cache.

Manage an explicitly approved rename, merge, supersession, discouragement, deprecation, or removal with compatibility routing and evidence-based exit criteria. Do not activate for ordinary edits, speculative consolidation, or a direct correction with no lifecycle impact.

Design, add, or amend tests for changed behavior with surface-appropriate coverage. Use when test design or test-file changes are part of the task; do not activate merely to run an existing test command, and use Playwright only when a browser-visible flow changed.

Perform an explicitly requested repository file-hygiene review or maintenance pass focused on factual accuracy, freshness, consistency, and duplicate or stale file prevention; read-only audits do not authorize corrections.

Use for designing and maintaining repository file structure for clarity, modularity, discoverability, and low-duplication across app and documentation surfaces.

Generate, validate, and enforce content-bound governance plans and exact-head release attestations for governed work. Use when governance tooling or CI enforcement is being run or debugged; do not activate for policy-only decisions, ordinary project tests, or routine validation.

Use for building and maintaining compact chat/session indexes (`docs/chat-history-index.md`) so long conversations can be queried precisely without re-reading broad transcript history.

Use for executing and enforcing governance tooling (artifact generation/validation/CI policy checks), including startup declaration checks, project-index sync checks, and repository skill-policy validation.

Use for converting ambiguous requests into explicit implementation contracts via assumptions, acceptance criteria, non-goals, constraints, and scope boundaries before major execution.

Use for selecting and enforcing the right process level across skills via deterministic risk scoring, mode-based gates, critical overrides, break-glass controls, ownership, and KPI review.

Use for minimizing token usage while preserving quality, through strict context filtering, indexed history retrieval, concise reasoning formats, output budgeting, and low-overhead execution patterns.

Use for managing the lifecycle of obsolete, superseded, merged, or renamed skills and docs with clear replacement paths, migration notes, validator warnings, and removal criteria.

Use for capping process overhead by task size, limiting skill count, validation depth, artifact creation, and user-facing ceremony before other governance or documentation skills expand scope.

Use for periodically reviewing which skills are overused, underused, missing, or creating friction by examining recent governance artifacts, handoffs, instruction trackers, and task outcomes.

Use for enforcing hard limits on cached artifacts, summaries, indexes, and other compact metadata files so they stay bounded and high-signal.

Use for selecting and enforcing the right process level across skills via deterministic risk scoring, mode-based gates, critical overrides, break-glass controls, ownership, and KPI review.

Use for executing and enforcing governance tooling (artifact generation/validation/CI policy checks), including startup declaration checks, project-index sync checks, and repository skill-policy validation.

Use for minimizing token usage while preserving quality, through strict context filtering, indexed history retrieval, concise reasoning formats, output budgeting, and low-overhead execution patterns.

Use for converting ambiguous requests into explicit implementation contracts via assumptions, acceptance criteria, non-goals, constraints, and scope boundaries before major execution.

Use for general Agent engineering work that needs a compact operating policy for clarification, sequencing, safe command execution, regression control, documentation upkeep, quality review, frontend judgment, and the persistent --quizme clarification mode.

Use for high-complexity Agent work that needs risk classification, auditability, validation evidence, documentation synchronization, directive tracking, and rollback-aware execution.

Use for low-complexity Agent work that needs concise responses, dependency-correct sequencing, and safe deterministic command execution without heavier governance.

Use for general Codex engineering work that needs a compact operating policy for clarification, sequencing, safe command execution, regression control, documentation upkeep, quality review, frontend judgment, and the persistent --quizme clarification mode.

Use for high-complexity Codex work that needs risk classification, auditability, validation evidence, documentation synchronization, directive tracking, and rollback-aware execution.

Use for low-complexity Codex work that needs concise responses, dependency-correct sequencing, and safe deterministic command execution without heavier governance.