Review
webern/cargo-readme
Reviews a GitHub pull request for correctness, architecture, security, backward compatibility, and test coverage.
Verify documentation and tests in fe-tools. An agent skill from MichealWayne/fe-tools.
Install Verify Docs Tests
$ npx skills add MichealWayne/fe-tools --skill verify-docs-tests -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install MichealWayne/fe-tools verify-docs-tests --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/MichealWayne/fe-tools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/utils/skills/verify-docs-tests .claude/skills/verify-docs-tests && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "verify-docs-tests" agent skill from https://github.com/MichealWayne/fe-tools/tree/master/utils/skills/verify-docs-tests into .claude/skills/verify-docs-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-docs-tests", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/MichealWayne/fe-tools/tree/master/utils/skills/verify-docs-testsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add MichealWayne/fe-tools --skill verify-docs-tests -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install MichealWayne/fe-tools verify-docs-tests --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MichealWayne/fe-tools.git skills-src && mkdir -p .agents/skills && cp -r skills-src/utils/skills/verify-docs-tests .agents/skills/verify-docs-tests && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "verify-docs-tests" agent skill from https://github.com/MichealWayne/fe-tools/tree/master/utils/skills/verify-docs-tests into .agents/skills/verify-docs-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-docs-tests", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add MichealWayne/fe-tools --skill verify-docs-tests -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install MichealWayne/fe-tools verify-docs-tests --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MichealWayne/fe-tools.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/utils/skills/verify-docs-tests .cursor/skills/verify-docs-tests && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "verify-docs-tests" agent skill from https://github.com/MichealWayne/fe-tools/tree/master/utils/skills/verify-docs-tests into .cursor/skills/verify-docs-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-docs-tests", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/MichealWayne/fe-tools.git --path utils/skills/verify-docs-tests--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add MichealWayne/fe-tools --skill verify-docs-tests -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install MichealWayne/fe-tools verify-docs-tests --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MichealWayne/fe-tools.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/utils/skills/verify-docs-tests .gemini/skills/verify-docs-tests && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "verify-docs-tests" agent skill from https://github.com/MichealWayne/fe-tools/tree/master/utils/skills/verify-docs-tests into .gemini/skills/verify-docs-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-docs-tests", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install MichealWayne/fe-tools verify-docs-testsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add MichealWayne/fe-tools --skill verify-docs-tests -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/MichealWayne/fe-tools.git skills-src && mkdir -p .github/skills && cp -r skills-src/utils/skills/verify-docs-tests .github/skills/verify-docs-tests && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "verify-docs-tests" agent skill from https://github.com/MichealWayne/fe-tools/tree/master/utils/skills/verify-docs-tests into .github/skills/verify-docs-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-docs-tests", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add MichealWayne/fe-tools --skill verify-docs-tests -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install MichealWayne/fe-tools verify-docs-tests --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MichealWayne/fe-tools.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/utils/skills/verify-docs-tests .opencode/skills/verify-docs-tests && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "verify-docs-tests" agent skill from https://github.com/MichealWayne/fe-tools/tree/master/utils/skills/verify-docs-tests into .opencode/skills/verify-docs-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-docs-tests", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
verify-docs-tests- GitHub stars
- 207
- Token cost
- ~281 tokens
- SKILL.md length
- 87 words
- Files
- 1
- Skills in repo
- 13
- Repo updated
- First seen
- Licence
- None found
At a glance
Verify documentation and tests in fe-tools. An agent skill from MichealWayne/fe-tools.
- Works in 4 steps: Check that exported APIs in… → Verify new or changed functions have… → Run tests and confirm they pass → …
- The user asks to verify docs/tests
- Calls npm
- Ensure exports and docs are aligned across utils
What it does
Verify Docs Tests is an agent skill from MichealWayne/fe-tools. Verify documentation and tests in fe-tools. Checks that exported functions have corresponding documentation and test coverage, validates JSDoc presence, and identifies missing tests. Use when the user asks to verify docs/tests, or ensure exports and docs are aligned across utils, web-utils, node-utils, canvas-utils, or ai-utils.
Its SKILL.md is about 280 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Technical documentation and Test coverage. It works with npm. The repository describes itself as: 前端开发常用文档/网站地址、样式/js方法封装库、项目模板。提供Chrome拓展程序.
When your agent uses it
- The user asks to verify docs/tests
- Ensure exports and docs are aligned across utils
Example prompts
- “/verify-docs-tests”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Check that exported APIs in packages//src/index.ts match documentation expectations. Compare exports against JSDoc coverage
- Verify new or changed functions have tests in packages//tests/. A function is untested if no describe('functionName') or…
- Run tests and confirm they pass
- If docs output is required, suggest npm run docs or use the sync-docs skill.
What it can do on your machine
Read from SKILL.md and the folder at commit 2f4fd1e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Verify Docs Tests loads about 281 tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 87 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 87 words (~281 tokens).
“Use the update-index-exports skill if exports are missing.”
- name
- verify-docs-tests
Files
Just SKILL.md in utils/skills/verify-docs-tests of MichealWayne/fe-tools.
Open the folder on GitHubat commit 2f4fd1e
Compare with similar skills
Verify Docs Tests next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Verify Docs Tests this skillMichealWayne/fe-tools | 207 | — | ~281 | Automated safety check: Pass | None | |
| Reviewwebern/cargo-readme | 385 | — | ~2k | Automated safety check: Notes | Apache-2.0 | |
| Testing GapsJamieMason/syncpack | 2.1k | — | ~766 | Automated safety check: Pass | MIT | |
| Write Testsryokun6/ryos | 1.3k | — | ~1.7k | Automated safety check: Pass | AGPL-3.0 | |
| Generate Testscoco-research/coco | 482 | — | ~1.7k | Automated safety check: Pass | Custom licence | |
| Activitypub TestingMicrock/ordinary-claude-skills | 403 | — | ~712 | Automated safety check: Pass | Custom licence |
Similar skills
Testing Gaps
JamieMason/syncpack
Run coverage, inspect results, and identify missing test scenarios for a given source file.
Write Tests
ryokun6/ryos
Write and run ryOS tests with Bun's native test runner (bun:test).
Generate Tests
coco-research/coco
A skill your agent uses when asked to generate tests for a file, module or component, to raise coverage, or to bootstrap a suite for untested code.
Activitypub Testing
Microck/ordinary-claude-skills
Testing patterns for PHPUnit and Playwright E2E tests. An agent skill from Microck/ordinary-claude-skills.
Test Coverage Analyzer
aiskillstore/marketplace
Analyzes test coverage gaps and suggests test cases for untested code paths.
More from MichealWayne/fe-tools
All 13 skills in this repoAdd Utils Function
MichealWayne/fe-tools
Add or modify utility functions in fe-tools. An agent skill from MichealWayne/fe-tools.
Select Package
MichealWayne/fe-tools
Choose the correct fe-tools package for new functionality. An agent skill from MichealWayne/fe-tools.
Fe Tools Frontend Resource Finder
MichealWayne/fe-tools
Recommend 3-5 targeted frontend resources from the fe-tools curated directory for a user's question.
Fe Tools Template Creator
MichealWayne/fe-tools
Extract a reusable project template from an existing codebase by removing business-specific code, preserving only the reusable engineering skeleton, and creating template usage docs such as README.
Fe Tools Template Recommender
MichealWayne/fe-tools
Recommend the most suitable project template or initialization path from fe-tools project-templates based on product, framework, runtime, and delivery constraints.
Add Tests
MichealWayne/fe-tools
Add or update Jest unit tests for fe-tools utilities. An agent skill from MichealWayne/fe-tools.
Related
Works with
Categories
Questions about Verify Docs Tests
What does Verify Docs Tests do?
Verify documentation and tests in fe-tools. An agent skill from MichealWayne/fe-tools. Verify Docs Tests is an agent skill from MichealWayne/fe-tools. Verify documentation and tests in fe-tools.
When should I use Verify Docs Tests?
Verify Docs Tests fits situations like: the user asks to verify docs/tests; ensure exports and docs are aligned across utils.
How do I install Verify Docs Tests in Claude Code?
Run `npx skills add MichealWayne/fe-tools --skill verify-docs-tests -a claude-code`. Or copy the skill folder (utils/skills/verify-docs-tests in MichealWayne/fe-tools) into .claude/skills/verify-docs-tests in your project. Claude Code loads it when a task matches its description.
How do I install Verify Docs Tests in Codex?
Run `npx skills add MichealWayne/fe-tools --skill verify-docs-tests -a codex`. Or copy the skill folder (utils/skills/verify-docs-tests in MichealWayne/fe-tools) into .agents/skills/verify-docs-tests in your project. Codex loads it when a task matches its description.
Can I use Verify Docs Tests in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add MichealWayne/fe-tools --skill verify-docs-tests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verify-docs-tests, .gemini/skills/verify-docs-tests, .github/skills/verify-docs-tests and .opencode/skills/verify-docs-tests in your project.
What does Verify Docs Tests need to run?
Going by SKILL.md and its folder, Verify Docs Tests needs the command-line tools its instructions call (npm).
Does Verify Docs Tests access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Verify Docs Tests safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Verify Docs Tests use?
No licence was found for Verify Docs Tests or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Verify Docs Tests use?
About 281 tokens (SKILL.md is roughly 1.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Verify Docs Tests?
Skills that share tags, products or a category with Verify Docs Tests: Review (webern/cargo-readme, 385 stars), Testing Gaps (JamieMason/syncpack, 2.1k stars), Write Tests (ryokun6/ryos, 1.3k stars) and Generate Tests (coco-research/coco, 482 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Verify Docs Tests?
MichealWayne (a GitHub user) maintains it in MichealWayne/fe-tools, which has 207 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on September 8, 2026.
Source: MichealWayne/fe-tools on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.