How do I install the Pre Completion Check skill?

Run npx skillmds@latest add tomevault-io/pre-completion-check in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pre Completion Check safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pre Completion Check?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pre Completion Check free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pre Completion Check?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pre Completion Check by tomevault-io

Name: Pre Completion Check
Author: tomevault-io

Pre Completion Check

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. Use when this capability is needed.

tomevault-io bd1ce97 2 files · 2.4 KB Updated Sep 17, 2026

File contents

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.

npm run lint — Biome lint
npm run lint:markup — Markuplint (also checks .stories.tsx)
npm run build — tsc && vite build (doubles as typecheck)
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 autodocs) 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.

Source: digital-go-jp/design-system-example-components-react — distributed by TomeVault.

Frequently asked questions