skills/claude-code/SKILL.md
# Snag — Visual Bug Tracker Review and manage visual bug reports captured with Snag. ## Data Location Issues are stored in `.snag/` in the current project root (automatically gitignored). Each issue is a pair of files: - `YYYY-MM-DD-HHMMSS-slug.md` — markdown with title, status, tags, details - `YYYY-MM-DD-HHMMSS-slug.png` — screenshot ## Commands - `/snag` or `/snag list` — Show all open issues with screenshots - `/snag all` — Show ALL issues (open + resolved) - `/snag done <slug>` — Mark
npx skillsauth add maciejgrabek/snag skills/claude-codeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Review and manage visual bug reports captured with Snag.
Issues are stored in .snag/ in the current project root (automatically gitignored). Each issue is a pair of files:
YYYY-MM-DD-HHMMSS-slug.md — markdown with title, status, tags, detailsYYYY-MM-DD-HHMMSS-slug.png — screenshot/snag or /snag list — Show all open issues with screenshots/snag all — Show ALL issues (open + resolved)/snag done <slug> — Mark a specific issue as resolved/snag done all — Mark all open issues as resolved.md files in .snag/ directory**Status:** open# heading).png file — the agent is multimodal and can display it)Edit the .md file and change:
**Status:** open
to:
**Status:** resolved
.png file.# Short description of the bug
**Captured:** 2026-02-19T14:30:27.000Z
**Status:** open
**Tags:** css, mobile

## Details
Optional longer description, steps to reproduce, expected behavior.
---
If Snag is running, issues are also available via HTTP at http://127.0.0.1:9999:
GET /api/issues?project={cwd}&status=open — list open issuesGET /api/issues/next?project={cwd} — get next issue to work onPATCH /api/issues/{id} with body {"project": "{cwd}", "status": "resolved"} — mark as resolvedFile-based access (reading .snag/ directly) is preferred — it requires no running server and works with any agent.
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
development
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.
development
End-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip verification under Parallels.