agentsclimarketplace

Author verify

Skill RachidChabane/agentsync/skills/author-verify

Fill in a repo's `verify` verb with its real fast checks (lint, typecheck, format). Use after scaffold-determinism creates a stub verify, or when a repo's commit gate has no real checks yet.From its SKILL.md

Install
npx -y skills add RachidChabane/agentsync --skill author-verify

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.6 KB, 387 tokens by cl100k_base, as published. Nobody here has run it

Author a repo's verify verb

The determinism commit gate runs verify before every agent commit. A stub verify that just passes gives no protection; the right checks are judgment (which of this repo's tools are fast and read-only) over a deterministic scan.

1. Scan for candidates (deterministic)

bash skills/author-verify/detect-tools.sh

It prints the repo's task runner and candidate fast checks (ruff, mypy, tsc, eslint, go vet, clippy, shellcheck, package.json scripts, …).

2. Decide (judgment)

Keep only checks that are fast and read-only/non-destructiveverify runs at commit time. Anything slow (full test suite, integration, e2e) belongs under test, not verify. Confirm each tool is actually configured for this repo, not just installed.

3. Write it into the front door

Put the chosen commands in the repo's verify verb, in whatever runner it uses:

  • Makefile → the verify: recipe
  • mise.toml[tasks.verify]
  • justfileverify:
  • package.json"scripts": { "verify": "..." }

Chain commands so any failure fails the verb (e.g. ruff check . && mypy .). If the repo has no front door yet, run scaffold-determinism first.

4. Prove it gates

Run the verb (make verify / mise run verify / …): it should pass on clean code. Introduce a deliberate lint error and confirm it now fails — that's what blocks a bad commit. Revert the error.

What ships with it: 1 file

1.9 KB alongside SKILL.md, 1 of them executable

Keep looking

Skills are one crate of 326,861. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.