guard

Scan changed files against known error patterns and extract root causes as new rules.

16|3|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/YehudaFrankel/clankbrain --skill guard-yehudafrankel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: guard
Source: https://github.com/YehudaFrankel/clankbrain/tree/main/.claude/skills/guard
Command: npx skills add https://github.com/YehudaFrankel/clankbrain --skill guard-yehudafrankel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scans recently changed files against a growing library of known error patterns, flags violations before they ship. After any bug fix, extracts the root cause as a new permanent rule. Trigger on "guard check", "scan for issues", "check conventions", "did I miss anything", "scan my changes".

Core Features & Use Cases

  • Scan: check recently changed files against all known error patterns
  • Learn: after any bug fix, extract the root cause as a new checkable rule so it never happens again
  • Use Case: integrate into CI to prevent regressions and automatically expand coverage as issues are fixed.

Quick Start

Run a guard scan after changes to identify violations, then enable learn mode to add a new rule from the root cause of a fix.

Frequently Asked Questions about guard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan recently changed code for regressions against known error patterns?

To scan recently changed code for regressions, trigger a guard check against your growing error-pattern library. The scan compares changed files against known patterns and flags violations before they ship.

Can I automatically extract bug root causes as new code review rules?

Yes, you can automatically extract bug root causes as new checkable rules during code review. After any bug fix, the learn mode extracts the root cause and appends it as a new permanent rule to guard-patterns.md.

How does an error-pattern library help prevent regressions in a CI pipeline?

An error-pattern library helps prevent regressions in a CI pipeline by scanning changed files against known issues before shipping. It automatically expands coverage by appending new rules extracted from fixed bugs.

What is the best way to grow a living rule library for code quality automation?

The best way to grow a living rule library for code quality automation is to enable learn mode after fixing bugs. This extracts the root cause of the fix and appends it as a new checkable rule to your patterns file.

Do I need any external dependencies to check conventions in my recent code changes?

No, you do not need external dependencies to check conventions in your recent code changes. The skill operates independently to scan changed files and append new rules to a local guard-patterns.md file.