meza

Symptom-based multi-agent code review. Use when the user asks to "run the review swarm", perform a symptom-based / multi-lens code review, or review a change through the review-swarm process. Launches the review-swarm Workflow (which fetches the symptom catalogue, fans out one investigator per symptom, and distills the findings), then presents the actionable review it returns.

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update an existing skill, run evals to test a skill, or benchmark skill performance with variance analysis.

Generate the final Conventional Commit message text by inspecting the intended git commit surface, with staged changes as the default source of truth. Use this whenever the user asks for a commit message, wants staged changes or the working tree summarized into a Conventional Commit, asks what type or scope to use, or needs help turning staged changes into release-note-ready commit text instead of code-level narration.

MUST USE when working with architectural decision records (ADRs). Triggers: evaluating whether a decision warrants an ADR (applying the severity gate), creating new ADRs, superseding existing ADRs, listing/reviewing ADRs, or linking related ADRs. The skill includes criteria for when NOT to create an ADR; not every architectural decision crosses the threshold.

Generate the final Conventional Commit message text by inspecting the intended git commit surface, with staged changes as the default source of truth. Use this whenever the user asks for a commit message, wants staged changes or the working tree summarized into a Conventional Commit, asks what type or scope to use, or needs help turning staged changes into release-note-ready commit text instead of code-level narration.

MUST CONSULT When asked to update and refresh dependencies in the project.

MUST use when updating this datapack for newer minecraft versions.

MUST use when updating this datapack for newer minecraft versions.

This is how you must conduct yourself when doing technical work. This skill is a methodology overlay that applies to any software task with real stakes: building features, fixing bugs, investigating production issues, designing systems, refactoring code, reviewing pull requests, choosing technology, or optimizing performance. If your task applies to this description, you must adhere to this skill.

Framework defining what good code looks like across all dimensions. MUST USE when writing, reviewing, or reasoning about code quality. Consult this skill to evaluate code against quality standards, make trade-off decisions, or understand what qualities to prioritize. Covers readability, correctness, reliability, operability, efficiency, maintainability, safety, and consistency.