agentleFS
woodbearywoodbeary/later-dog/skills/laterdog/maintain-verification-skill/SKILL.md

maintain-verification-skill

Skill2 starsChanged 29 days agoApache-2.0View on GitHub

Keep a repository's verification skill and feature map in step with the app: update them when the app changes or a recipe stops working, and re-prove what you touched.

81 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-pstack, principle-explain-the-number and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • bnemaSkill

    setup-pstack

    Configure which Pi models pstack uses per role. Detects available provider/model specs and writes pstack's user configuration. Use for /setup-pstack, "configure pstack models", or changing pstack model choices.

    Also in 30 projects that use this

  • shiwenbin1617Skill

    principle-explain-the-number

    Apply before you measure, and before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.

    Also in 33 projects that use this

  • shiwenbin1617Skill

    poteto-help

    Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.

    Also in 16 projects that use this

  • eryzerzSkill

    make-bot-ui

    Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.

    Also in 21 projects that use this

  • drafaelSkill

    in-your-own-words

    Restate the user's goals and the problem they are trying to solve to check understanding. Manual invocation only; use when the user explicitly invokes in-your-own-words or requests this understanding check. Do not solve the task or rewrite the assistant's last answer.

    Also in 30 projects that use this

  • instructureSkill

    ketchup

    Rebuild context after /clear by analyzing uncommitted changes across Canvas LMS and all plugin repositories

    Also in 25 projects that use this

  • +3 more from shiwenbin1617

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 81 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when a change moves a route, command, screen, label or side effect that a verification skill describes, or when following one of its …

    line 8
  2. Distinctive:

    Decide what is wrong: If a recipe fails because the product is broken, report the bug with its evidence.

    line 13

“Common” is measured: kept by at least 6 in 10 of the 81 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Maintain verification skill

Use when a change moves a route, command, screen, label or side effect that a verification skill describes, or when following one of its recipes fails.

Procedure

  1. Read what exists first: the verification skill and its feature map. For later.dog itself these are docs/verification/README.md and its feature pages, docs/laterdog/verification.md, and the canonical skills/laterdog/verify-laterdog/ (exported by pnpm laterdog:skills; never edit the exports).
  2. Decide what is wrong. If a recipe fails because the product is broken, report the bug with its evidence. Do not rewrite the recipe until it passes.
  3. Match the change to the map. List the routes, commands, entry points and side effects the change touched, and find each one's entry. Add entries for new surfaces, including second ways in (a menu item, a shortcut, an MCP tool). Before deleting a stale entry, search for anything that links to it or runs it.
  4. Correct commands by running them against the real app in an isolated instance, not by reading the code alone.
  5. Re-prove the affected features in an isolated fixture. Keep the evidence where cleanup does not reach, and write down what the fixture cannot show.
  6. Keep claims in their lane. A fixture passing shows the implementation behaves. Fixture success does not qualify a live provider, a real account or production.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.