agentleFS
yusufalikyncyusufalikync/ccs/.claude/skills/verify/SKILL.md

verify

Skill4 starsChanged 9 months agoMITView on GitHub

Run full project verification — smoke tests, CLI checks, and code quality

189 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use genie-hacks, workfly and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • automagik-devSkill

    genie-hacks

    Browse, search, and contribute community hacks — real-world patterns for provider switching, teams, skills, hooks, cost optimization, and more.

    Also in 3 projects that use this

  • automagik-devSkill

    workfly

    Discover a procedure and build its saved workflow — dynamic discovery, drafted script, adversarial verification, landed in the catalog.

    Also in 3 projects that use this

  • TheKREATORSSkill

    instinct-export

    Export instincts from project/global scope to a file

    Also in 3 projects that use this

  • TheKREATORSSkill

    instinct-import

    Import instincts from file or URL into project/global scope

    Also in 3 projects that use this

  • AviadPSkill

    risk-assess

    Assess the risk and blast radius of a proposed code change before implementing it. Evaluates CI impact, framework-wide vs localized scope, rollback path, and identifies blindspots. Use when user says "what's the risk", "is this safe", "assess the impact", "risk assess", "blast radius", or before applying framework-wide or CI-affecting changes. Do NOT use for code quality review (use code-quality) or plan validation (use design-validator).

    Also in 3 projects that use this

  • diego-tobalinaSkill

    build-fix

    Fix build and compilation errors systematically. Run when build fails.

    Also in 6 projects that use this

  • +2 more from automagik-dev
  • +1 more from TheKREATORS

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 168 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run all checks in sequence and report results.

    line 11
  2. Distinctive:

    All tests must pass.

    line 19
  3. Distinctive:

    After install: status should show ACTIVE

    line 28
  4. Distinctive:

    After uninstall: status should show NOT INSTALLED

    line 29
  5. Very specific:

    Verify these are included: bin/cli.js, src/, scripts/statusline.js.

    line 38

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

Run all checks in sequence and report results.

Instructions

1. Smoke tests

npm test

All tests must pass.

2. Install cycle

node bin/cli.js install
node bin/cli.js status
node bin/cli.js uninstall
node bin/cli.js status
  • After install: status should show ACTIVE
  • After uninstall: status should show NOT INSTALLED

3. console.log check

Grep scripts/statusline.js for console.log. It must NOT contain any — only process.stdout.write() is allowed.

4. Package check

npm pack --dry-run

Verify these are included: bin/cli.js, src/, scripts/statusline.js. Verify scripts/smoke-test.js is NOT included (excluded by design — only scripts/statusline.js is in the package).

5. No hardcoded paths

Grep src/ files for hardcoded ~/.claude or /tmp/ paths. All paths should come from src/paths.js or os.tmpdir().

Output

Report each check as:

  • PASS: Check description
  • FAIL: Check description — what went wrong and how to fix

Final summary: X/5 checks passed.

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.