agentleFS
chryzxcchryzxc/herm/.agents/skills/verify-change/SKILL.md

verify-change

Skill45 starsChanged 22 days agoMITView on GitHub

Verify a Herm code change before calling it done — pick the focused test suite, build, and check the Definition of Done without slow full runs or relaunching the app. Use after editing Swift sources or tests.

23 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check the Definition of Done in STANDARDS.md: README/DESIGN updated for user-visible changes, no credential-shaped values, and …

    line 16
  2. Very specific:

    Do not run the full suite, make check, or make package locally unless the user asks.

    line 20

“Common” is measured: kept by at least 6 in 10 of the 19 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

Verify a Herm change

  1. Build: swift build --disable-automatic-resolution.
  2. Find the focused suite: match the changed type to its tests (grep -rl "<TypeName>" Tests/HermTests), then run swift test --disable-automatic-resolution --filter '<Suite>|<OtherSuite>'. Native UI fixtures share the main actor; add --no-parallel if they time out.
  3. Generative UI changes: also run the CI job's filter GenerativeUIIsolationTests|GenerativeUITests|GeneratedHTMLTests.
  4. Run git diff --check.
  5. Check the Definition of Done in STANDARDS.md: README/DESIGN updated for user-visible changes, no credential-shaped values, and layout-stability rules respected.

Do not run the full suite, make check, or make package locally unless the user asks; CI runs them. Never run make run or Scripts/run-debug-app.sh unprompted, because it kills the user's live agents. Report which suites ran and their result, including failures verbatim.

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.