agentleFS
Sign inStart free
skyelan1999skyelan1999/aide/.agents/skills/aide-verification-docs/SKILL.md

aide-verification-docs

Skill4 starsChanged 31 days agoMITView on GitHub

Validate Aide changes, reproduce bugs, update implementation docs, maintain task evidence, or prepare handoff. Load for QA and documentation tasks.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep evidence factual: record environment, command, result, and limits.

    line 9
  2. Very specific:

    Update the current docs to match implemented behavior, link sources, and distinguish available capability from tested capability.

    line 10

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “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

Aide verification and documentation

  • Derive checks from the acceptance criteria and changed call paths; select focused tests first, then the repository quick/full profile as appropriate.
  • Keep evidence factual: record environment, command, result, and limits. Static inspection is not runtime acceptance; a rendered page is not proof of persistence or API behavior.
  • Update the current docs to match implemented behavior, link sources, and distinguish available capability from tested capability. Run python3 scripts/check_docs.py after Markdown edits.
  • UI claims require actual browser interaction. If a capability or environment is unavailable, report NOT_RUN and name the next verification owner/action.

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.

Check your setup, free