← ClaudeAtlas

guard-authoringlisted

Author, approve, and maintain project guard profiles (.wipnote/guard-profile.yaml). Use for custom quality/completion/yolo gates, polyglot monorepo per-directory guards, re-approving after drift, and understanding the trust boundary and autodetection fallback.
shakestzd/wipnote · ★ 3 · API & Backend · score 69
Install: claude install-skill shakestzd/wipnote
# Guard Authoring Skill **Trigger keywords:** guard profile, guard init, quality gate, completion gate, yolo gate, applies_when, guard authoring, re-approve guard, guard drift --- ## What a guard profile is `.wipnote/guard-profile.yaml` is a hand-maintained YAML file committed to the repository. It replaces wipnote's manifest autodetection with an explicit, version-controlled list of commands. Treat it like any other config file — diff it, review it in PRs, edit it when your toolchain changes. See `docs/guard-profiles.md` for the full reference. --- ## Schema ```yaml guards: quality: # run by `wipnote check --gate` - name: go-build # short identifier (required) cmd: go build ./... # shell command (required, non-empty) cwd: backend # repo-root-relative working dir (optional) applies_when: # narrow when guard is active (optional) paths: ["backend/**/*.go"] # ** matches zero or more path segments completion: # work-item completion gate - name: go-test cmd: go test ./... yolo: # per-commit gate in yolo sessions - name: go-vet cmd: go vet ./... approved: signature: "sha256:..." # content hash; written by wipnote, never by hand by: "Alice" at: "2026-01-15T10:30:00Z" ``` Fields: `name` (required), `cmd` (required, non-empty), `cwd` (optional, repo-root-relative), `applies_when.paths` (optional forward-slash globs — `**` crosses `/`,