# Did you know you can turn your verification checks into Claude Code skills? Hi, it's me, I'm so excited! Today I found something that should really click for anyone using Claude Code. The manual checking you do by hand every time can actually be handed off to skills! ## What was announced? According to the Claude Blog, there's a new writeup on turning "verification loops" in Claude Code into skills. A verification loop is a repeating cycle where an AI agent checks its own work — running tests, linters, or custom checks — and fixes what fails before moving on. Claude Code already ships with a handful of built-in verification tools, and the article's whole point is to build on top of those and turn your own verification loop into a skill. ## Why it matters Claude Code already has several verification mechanisms built in. - **The /verify skill** — builds and runs your app, then observes the resulting changes - **Toolchain integration** — catches error codes and warnings from linters and build tools - **Code Review (research preview)** — an automated PR review service - **GitHub Actions integration** — runs verification on every push or PR - **Spec validation** — checks changes against a markdown specification - **Rubrics in Claude Managed Agents (beta)** — a grader agent evaluates the work and can trigger an automatic rework loop Even with all of that in place, project-specific checks still tend to fall on a human to verify by hand, every single time. The article's premise is that if you write down the correction patterns you repeat yourself, as a skill, Claude can take over the checking-and-fixing part. ## What changes If you write down the pattern you keep pointing out — "the one I always catch" — in plain language, you can hand it to Claude the same way you'd brief a new teammate on day one. The article notes that deterministic, project-specific rules that generic linters miss are especially good candidates for automation. "Reject any migration that drops a column without a backfill step" is given as exactly that kind of example. ## Dive Deep The article describes two ways to create a skill. - **Using the skill-creator plugin** — asking something like `/skill-creator Create a skill for verifying frontend changes end-to-end. Interview me about my workflow.` interviews you about your workflow and builds the skill for you - **Creating it manually** — placing a markdown file in the `.claude/skills/` directory, with frontmatter (name, description, allowed-tools) followed by plain-language verification instructions Four deployment patterns are covered for how to run these skills once they exist. - **Standalone** — deliberately invoked for cross-cutting checks, such as security scans, accessibility audits, or license verification - **Embedded** — runs automatically as part of a producing skill's workflow, by appending verification steps to an existing skill's body - **Chained** — one skill calls another on completion, so multiple verified handoffs run end-to-end. The article warns that "chained verification loops can increase token spend, so it's best to test these loops before deploying them broadly" - **On every PR** — team-wide automation where the same procedures apply to every pull request regardless of author The suggested workflow is: identify the repetitive manual follow-ups from your recent work, try the built-in `/verify` skill first, document the procedure in plain language, create the skill using skill-creator or by hand, test it on new tasks and iterate, then experiment with chaining skills together for end-to-end flows. The article wraps up with this line. > The more you can encode for Claude to follow, the more often Claude's response will land closer to what you want on the very first try. ## Wrap-up - A verification loop is a cycle where Claude checks its own work with tests or linters, then fixes failures before moving on - Claude Code already has multiple verification mechanisms, including /verify, GitHub Actions integration, and Code Review (research preview) - Writing down the project-specific rules you keep correcting by hand, as a skill, lets Claude take over that checking role - Skills can run standalone, embedded, chained, or on every PR - If you use Claude Code day to day, it's worth turning your "usual fix" into a skill!