Domains
Forms
Mechanism
Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.
When reviewing pull requests, establishing team review standards, mentoring developers, or conducting architecture/security reviews.
Constructive, prioritized feedback that catches bugs early, shares knowledge, maintains morale, and produces clear approve/comment/request-changes decisions with review guidelines.
Use Cases
A tech lead receives a 600-line PR from a junior dev. Using this skill, they run the four-phase review: gather context, assess architecture, inspect line-by-line for security and edge cases, then summarize with severity labels. They ask guiding questions instead of commanding changes. Result: bugs caught early, junior dev learns, and PR is approved faster with clear actionable feedback.
A team wants to standardize reviews across repos. Using this skill, they adopt the checklist method and severity labels as team guidelines, and apply the question approach in mentoring. This reduces nitpick conflicts, shortens cycle time, and builds a knowledge-sharing culture with consistent quality gates and less morale damage.
Skill Relationships
Dependency relationships read as "the upper tier points to the lower tier." The current Skill sits in the middle tier — above are Skills that depend on it, below are Skills it depends on.
Tier 1 · These Skills Use Me
Tier 2 · Current Skill
Tier 3 · I Use These Skills
Browse this skill's relationships within its skillset. Click a node to switch the side panel; use the search box to jump to any skill.
Skill File
