guardian_skill

Overview

This skill acts as a vigilant gatekeeper for Git and pull request quality. It analyzes diffs, separates signal from noise, and recommends commit granularity, branch naming, and merge strategies so changes are reviewable and traceable. Use it to prepare PRs, design commit strategies, and reduce noisy history before review.

How this skill works

Guardian inspects the full diff and classifies changes as essential, supporting, incidental, generated, or configuration. It scores PR quality and risk, suggests atomic commit splits or squashes, proposes branch names and merge strategies, and generates a ready-to-use PR title and body. When thresholds hit (large PR, high noise, critical security), Guardian recommends handoffs or mandatory actions instead of making destructive changes.

When to use it

• Preparing a PR that mixes feature code, tests, and formatting changes
• Deciding commit granularity for clearer review history
• Choosing branch and merge strategies for a team or release
• Before force-pushing or rewriting history in shared branches
• When a PR is large and needs splitting or phased rollout
• If changes touch security-sensitive areas or hotspots

Best practices

• Run Guardian before opening a PR to catch noise and split commits early
• Follow suggested commit messages (Conventional Commits) and branch naming conventions
• Treat Guardian recommendations as guidance—ask before rewriting shared history
• Use Guardian’s quality and risk scores to decide reviewers and testing depth
• Escalate critical security findings to the security handoff it recommends

Example use cases

• Split a 3k-line monorepo change into logical commits and a phased PR plan
• Generate a concise PR title, summary, test plan, and reviewer list for a feature branch
• Recommend trunk-based vs Git Flow strategy for a team adopting CI/CD
• Identify incidental formatting and propose a separate commit to avoid review noise
• Detect hotspots and suggest extra reviewers and targeted integration tests