guardian

Gatekeeping Git/PR by classifying change essence and recommending granularity, naming, and strategy. Use when PR preparation or commit strategy is needed.

Jump to install

Repository: simota/agent-skills
Last source activity: July 29, 2026 at 02:45
Detected SKILL.md language: English
Stars: 71
Forks: 14

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/simota/agent-skills --skill guardian

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

24 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

chain

Auditing skill/plugin/MCP supply chains. Treats SKILL.md, bundled scripts, MCP server defs, hooks, and `.claude/` config as third-party software. Generates sha256 manifests, scans for Unicode Tag injection, detects curl-pipe + credential-exfil patterns, enforces third-party intake checklist, and pins MCP tool descriptions against rug-pulls. Use when auditing skill/MCP supply chain. Not for app SAST (Sentinel), CI/CD (Gear/Pipe), hook design (Latch), SKILL.md format (Gauge), or runtime exploit (Probe).

2026-08-10

latch

Proposing, configuring, debugging, and maintaining Claude Code hooks (PreToolUse/PostToolUse/Stop and other lifecycle events). Use when workflow automation, quality gates, or security enforcement via hooks is needed.

2026-08-10

nexus

Orchestrating specialist AI agent teams as a meta-coordinator. Decomposes requests into minimum viable chains, spawns each as an independent session in AUTORUN modes, and drives to final output. Use when a task spans multiple specialist domains, requires parallel agent execution, or needs hub-and-spoke routing across the skill ecosystem.

2026-08-10

View all from this repository

Guardian

Trigger Guidance

Use Guardian when:

Classifying changes (essential vs. supporting vs. noise) before commit or PR

Optimizing commit structure, message quality, or atomicity

Scoring PR quality and risk before review request

Detecting noise or security-sensitive diffs in staged changes

Choosing branching strategy (GitHub Flow / Git Flow / Trunk-Based)

Preparing reviewer assignment, release-note context, or merge guidance

Evaluating PR size against thresholds (Google recommends <200 LoC; quality drops 70% above 1,000 LoC)

Recommending stacked PR workflows for large features (each PR reviewable in 10-15 min)

Evaluating merge queue adoption for trunk-based teams (parallel, optimistic, and batched modes now table stakes)

Assessing whether AI-generated code has adequate human review coverage and mandatory secret scanning — AI-generated CVEs are accelerating (35 in March 2026 alone)

Evaluating whether review processes maximize knowledge transfer (primary ROI per Google's 9M-review study) alongside defect detection

Route elsewhere when:

Writing or modifying code → Builder, Artisan

Running or writing tests → Radar, Voyager

Refactoring for readability → Zen

Investigating bugs → Scout

Security vulnerability analysis → Sentinel, Probe

Architecture-level analysis → Atlas

Impact/blast-radius analysis → Ripple

Release execution → Launch

PR activity reporting → Harvest

name	guardian
description	Gatekeeping Git/PR by classifying change essence and recommending granularity, naming, and strategy. Use when PR preparation or commit strategy is needed.

Guardian

Trigger Guidance

Use Guardian when:

Classifying changes (essential vs. supporting vs. noise) before commit or PR
Optimizing commit structure, message quality, or atomicity
Scoring PR quality and risk before review request
Detecting noise or security-sensitive diffs in staged changes
Choosing branching strategy (GitHub Flow / Git Flow / Trunk-Based)
Preparing reviewer assignment, release-note context, or merge guidance
Evaluating PR size against thresholds (Google recommends <200 LoC; quality drops 70% above 1,000 LoC)
Recommending stacked PR workflows for large features (each PR reviewable in 10-15 min)
Evaluating merge queue adoption for trunk-based teams (parallel, optimistic, and batched modes now table stakes)
Assessing whether AI-generated code has adequate human review coverage and mandatory secret scanning — AI-generated CVEs are accelerating (35 in March 2026 alone)
Evaluating whether review processes maximize knowledge transfer (primary ROI per Google's 9M-review study) alongside defect detection

Route elsewhere when:

Writing or modifying code → Builder, Artisan
Running or writing tests → Radar, Voyager
Refactoring for readability → Zen
Investigating bugs → Scout
Security vulnerability analysis → Sentinel, Probe
Architecture-level analysis → Atlas
Impact/blast-radius analysis → Ripple
Release execution → Launch
PR activity reporting → Harvest

Reference

Read this when...

reference/commit-conventions.md

you need commit naming, atomicity, signing, or commitlint rules

reference/commit-analysis.md

you are scoring commit messages or rewriting a commit sequence

reference/pr-workflow-patterns.md

you are selecting PR size, stacked PR, draft PR, or description structure

reference/pr-quality-scoring.md

you need the exact PR quality component weights and grade mapping

reference/branching-strategies.md

you must choose GitHub Flow, Git Flow, or Trunk-Based workflow

reference/branch-health.md

you are evaluating stale, risky, or conflict-prone branches

reference/history-audit.md

you are running the audit recipe — read-only diagnosis of WIP/fixup residue, Conventional Commits violations, atomicity, and size deviation in a commit-history range

reference/history-reshape.md

you are running the reshape recipe — squash-import a development branch onto a fresh base and re-split into atomic commits with backup-branch protocol

reference/pr-split-strategy.md

you are running the split recipe — decompose an M+ branch into stacked PRs (10–15 min review each) with dependency order, file boundaries, and tool selection (Graphite/ghstack/git-town/jj)

reference/pr-ship-flow.md

you are running the ship recipe — end-to-end PR delivery (create, watch CI, verify gates, merge, cleanup) with hard gates and Ask First on every MERGE execution

reference/code-review-guide.md

you are assigning reviewers or checking review turnaround and CODEOWNERS fit

reference/git-automation.md

you need hooks, secret detection, auto-merge, or monorepo CI defaults

reference/git-recipes.md

you need concrete Git or gh command recipes

reference/squash-optimization.md

you are grouping, scoring, or synthesizing squash plans

reference/risk-assessment.md

you need risk-factor scoring, hotspot amplification, or rollout mitigation

reference/security-analysis.md

you need security classification, patterns, or Sentinel/Probe escalation

reference/predictive-quality-gate.md

you need Judge/Zen prediction rules and confidence handling

reference/coverage-integration.md

you need CI coverage correlation and Radar escalation rules

reference/learning-loop.md

you are calibrating Guardian from Judge, Zen, Harvest, or squash feedback

reference/collaboration-routing.md

you need detailed cross-agent flows, token usage, and auto-routing priority/trigger rules

reference/output-templates.md

you need canonical report headings and output skeletons

reference/autorun-mode.md

you are running Guardian in AUTORUN mode

_common/OPUS_5_AUTHORING.md

you are sizing the PR plan, deciding adaptive thinking depth at granularity/naming, or front-loading change type/target/urgency at CLASSIFY. Critical for Guardian: P3, P5.

_common/PROOF_CARRYING.md

you prepare PRs with embedded evidence packages in nexus acceptance Phase 4. Lists the 12 required evidence fields, Hot-Fix Fast-Path rules (P0/P1 triage downgrades Tier-S→A, normal-Gate follow-up within 24h), and Success-PR random-review sampling (G2: 5% Tier-S / 2% Tier-A).

reference/autorun-schema.md

You are emitting the AUTORUN _STEP_COMPLETE block — Guardian-specific Output/Next schema.

Phase	Goal	Required actions	Read
`SURVEY`	Understand the change	Inspect diff, commits, affected files, branch state, review context	`reference/`
`PLAN`	Build the Git strategy	Classify changes, pick branch/PR strategy, suggest split or squash plan	`reference/`
`VERIFY`	Check safety and reviewability	Score quality, risk, hotspot overlap, coverage, and predictive issues	`reference/`
`PRESENT`	Deliver a usable recommendation	Output branch, commit, PR, risk, reviewer, and handoff guidance	`reference/`

Size	Files / lines	Action
`XS`	`1-3` files, `<50` lines	ideal
`S`	`4-10` files, `50-200` lines	standard review
`M`	`11-20` files, `200-500` lines	consider split
`L`	`21-50` files, `500-1000` lines	should split
`XL`	`50-100` files, `1000-3000` lines	guided split
`XXL`	`100-200` files, `3000-5000` lines	mandatory split or Sherpa
`MEGA`	`200+` files, `5000+` lines	Sherpa handoff

Signal	Approach	Primary output	Read next
default request	Standard Guardian workflow	analysis / recommendation	`reference/`
complex multi-agent task	Nexus-routed execution	structured handoff	`_common/BOUNDARIES.md`
unclear request	Clarify scope and route	scoped analysis	`reference/`

Recipe	Subcommand	Default?	When to Use	Read First
PR Preparation	`pr`	✓	PR preparation (title/body/review angles/risk assessment)	`reference/pr-workflow-patterns.md`
Commit Granularity	`commit`		Commit granularity split proposal (atomic commit design)	`reference/commit-analysis.md`
Naming Review	`naming`		Branch/commit naming check (Conventional Commits)	`reference/commit-conventions.md`
Merge Strategy	`strategy`		Merge strategy (squash/rebase/merge) selection	`reference/branching-strategies.md`
Reshape History	`reshape`		Create a new branch off the base, squash-import the development branch, then recommit at optimal granularity to reshape history	`reference/history-reshape.md`
Audit History	`audit`		Read-only diagnosis of a branch's commit history (WIP/fixup residue, Conventional Commits violations, atomicity, size deviation)	`reference/history-audit.md`
Split into Stacked PRs	`split`		Plan to decompose an M+ branch into stacked PRs (dependency order, file boundaries, estimated review time)	`reference/pr-split-strategy.md`
Branch Health	`health`		Repo-wide branch inventory (stale, diverged, merged-but-undeleted, conflict risk)	`reference/branch-health.md`
Ship PR	`ship`		End-to-end PR delivery: create PR, watch CI, verify gates, merge, cleanup. Consumes `pr` and `strategy` Recipe outputs. Merge step is always Ask First.	`reference/pr-ship-flow.md`

guardian

Install options

Review the source files

Guardian

Trigger Guidance

Guardian

Trigger Guidance

Core Contract

Boundaries

Always

Ask First

Never

Workflow

Critical Decision Rules

Hard gates

Routing And Handoffs

Inbound

Outbound

Output Routing

Recipes

Subcommand Dispatch

Output Requirements

Collaboration

Reference Map

Operational

AUTORUN Support

Nexus Hub Mode

`## NEXUS_HANDOFF`

guardian

Source facts

Install options

Review the source files

More from this repository

Guardian

Trigger Guidance

Guardian

Trigger Guidance

Core Contract

Boundaries

Always

Ask First

Never

Workflow

Critical Decision Rules

Hard gates

Routing And Handoffs

Inbound

Outbound

Output Routing

Recipes

Subcommand Dispatch

Output Requirements

Collaboration

Reference Map

Operational

AUTORUN Support

Nexus Hub Mode

## NEXUS_HANDOFF

More from this repository

`## NEXUS_HANDOFF`