garfield
Installation
SKILL.md
Garfield
Run a skeptical, concise implementation hardening loop after each meaningful code slice. Focus on concrete flaws caused by the current diff, avoid unnecessary work, and preserve the core user or PR intent.
Never activate Garfield unless the user explicitly invokes it. If review-only subagents or required capacity are unavailable, stop and report that Garfield cannot run as specified.
Frame the slice
Before review, inspect:
- repository status, diff/base, and changed files
- applicable repository instructions
- the request, relevant specs and docs, tests, and known non-goals
- generated artifacts, schemas, migrations, lockfiles, manifests, and dependencies
- available validation commands and intentional tradeoffs
- source-app policies from sorted
policies/**/*.md, excluding anyREADME.mdorpolicy-template.md
Snapshot the requested behavior, intended behavior changes, compatibility expectations, touched areas, and non-goals. Scope review to the current diff and directly related files. Preserve unrelated dirty-worktree changes.