agentleFS
Sign inStart free
digital-go-jpdigital-go-jp/design-system-example-components-react/.agents/skills/pre-completion-check/SKILL.md

pre-completion-check

Skill685 starsChanged 26 days agoMITView on GitHub

Run the pre-completion checks before declaring a task done. Executes lint, markup lint, build (tsc), tests, and reminds the user to verify Storybook visually.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run each command and report pass/fail.

    line 13

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Context

  • Current branch: !git branch --show-current
  • Changed files: !git status --short

Steps

Run each command and report pass/fail. If any command fails, stop and surface the failure to the user before continuing.

  1. npm run lint — Biome lint
  2. npm run lint:markup — Markuplint (also checks .stories.tsx)
  3. npm run build — tsc && vite build (doubles as typecheck)
  4. npm test — Vitest (unit + Storybook). To scope to one component while iterating, pass the path through npm with --: npm test -- src/components/Foo (don't call npx vitest directly — stay on the project's npm script).

Manual checks (remind the user)

These cannot be automated; list them so the user can confirm before merging:

  • Storybook started locally (npm run storybook) and each affected Story (including its .mdx docs page, if any) was visually verified.
  • For ports: compared against the HTML reference side-by-side.
  • WCAG 2.2 AA criteria relevant to the change are satisfied.
  • Keyboard navigation works end-to-end for any interactive element added or changed.
  • No console.log or other debug output left in the diff.
  • No new runtime or dev dependencies were added without user approval.

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