biome-enforcement
Biome Enforcement
This skill governs how agents should work with Biome as a repository enforcement tool.
It still preserves the core rule from the prior skill:
- Biome is primarily a final remediation and enforcement pass
- the required final command remains fixed
- the remediation loop remains mandatory
- post-Biome build and test re-validation still occurs only when Biome changed files
This skill is broader than a single final step. Agents should also use it when they need to:
- reason about whether a task is Biome-relevant
- interpret Biome JSON diagnostics
- decide whether generated output belongs in ignore rules
- update Biome configuration safely
- distinguish source issues from tool-noise issues before the final pass
More from mwillbanks/agent-skills
code-discipline
Prevent trivial helpers, wrapper layers, rename-only utilities, duplicate constants, and local reinvention. Enforce reuse of platform primitives, framework capabilities, shared utilities, and proven libraries. Use when adding or reviewing logic, constants, composition, or UI structure so the agent keeps code disciplined and avoids technical debt.
32agent-execution-mode
Enforces complete execution, repository-aware spec-driven delivery, mode-aware delivery, compact sub-agent communication, independent agent-review gating, validation, and reporting for implementation, bugfix, hardening, documentation, specification, architecture, design, review, and post-mortem tasks. Use whenever work must be completed, reviewed, validated, or documented through an explicit execution mode instead of handled ad hoc.
31repo-standards-enforcement
Use this skill to enforce repository-wide standards for toolchain compliance, package-manager purity, type safety, testing, maintainability, and architecture. When a more specific skill exists for a concern such as final linting or formatting remediation, that more specific skill takes precedence over this skill's generalized guidance.
26execution-alignment-gate
Detects materially ambiguous or under-specified requests, selects the right clarification target, and enforces bounded alignment before execution, including spec-governed continuations and approval-gated manager handoffs. Use when ambiguity could cause wrong deliverables, wrong scope, wrong implementation path, avoidable rework, or token waste from repeated follow-up.
19speckit-feature-orchestrator
Orchestrates a full Speckit feature workflow from constitution amendment through specification, clarification, plan, tasks, and analysis as a chief-architect governor using subagents. Use when the repository already uses Speckit or the user explicitly asks for Speckit and wants to discuss, refine, or directly drive a new feature into implementation-ready Speckit artifacts in one controlled pass.
12review-remediation-gate
Close review findings deterministically, remediate blocking issues, and prove review closure. Use when the user says to fix review comments, address review findings, run a review-remediation pass, close out blockers, or finish work only after review issues are resolved.
7