Agent skill

Verify

by jh941213 in jh941213/my-cc-harness

Code verification after task completion (typecheck, lint, test, build).

No licenceAuto-check: notesTesting & QA

Install Verify

skills CLI
$ npx skills add jh941213/my-cc-harness --skill verify -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jh941213/my-cc-harness verify --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jh941213/my-cc-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills_en/verify .claude/skills/verify && rm -rf skills-src

Use ~/.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/

Facts

Skill name
verify
GitHub stars
126
Token cost
~1.1k tokens
SKILL.md length
373 words
Files
1
Skills in repo
62
Repo updated
First seen
Licence
None found

At a glance

Code verification after task completion (typecheck, lint, test, build).

  • Works in 3 steps: Project Detection → Verification Order (fix immediately on… → Result Report
  • Tasks that involve Linting and formatting
  • SKILL.md covers Step 1: Project Detection, Step 2: Verification Order…, Step 3: Result Report and Fix Strategy by Error Category, plus 1 more section
  • Calls npx, go and cargo

What it does

Verify is an agent skill from jh941213/my-cc-harness. Code verification after task completion (typecheck, lint, test, build). Triggers on: verify, run tests, check build, typecheck. NOT for: E2E tests, code writing, implementation.

Its SKILL.md is about 1.1k 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 Linting and formatting and End-to-end testing.

When your agent uses it

  • Tasks that involve Linting and formatting
  • Tasks that involve End-to-end testing

Example prompts

  • “/verify”

Requirements

  • Python 3
  • Node.js
  • Pre-approved tools (allowed-tools): Read, Bash, Grep, Edit

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Project Detection
  2. Verification Order (fix immediately on failure)
  3. Result Report

What it can do on your machine

Read from SKILL.md and the folder at commit e9210e2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Bash
    • Grep
    • Edit

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx
    • go
    • cargo
    • ruff
    • pytest
    • npm
    • python3
    • gitleaks
    • mypy

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx and 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 loads about 1.1k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 373 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~46
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Bash, Grep, Edit

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 373 words (~1,074 tokens).

“Verifies code after task completion. Run in order; proceed to the next step only after the current one passes.”

— opening of SKILL.md by jh941213
name
verify
allowed-tools
Read, Bash, Grep, Edit
user-invocable
true
disable-model-invocation
false

Read the full SKILL.md on GitHub

Files

Just SKILL.md in skills_en/verify of jh941213/my-cc-harness.

Open the folder on GitHubat commit e9210e2

Compare with similar skills

Verify 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.

Verify compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Verify this skilljh941213/my-cc-harness126—~1.1kAutomated safety check: NotesNone
Acceptance Test Authoringintent-driven-dev/intent-driven-template161—~2kAutomated safety check: PassMIT
Odc DebuggingDouglasNeuroInformatics/OpenDataCapture119—~2.8kAutomated safety check: NotesApache-2.0
Setup Codebase HarnessAI-Builder-Club/skills1.3k—~1.4kAutomated safety check: PassNone
Pierre Testing and Verification Guidepierrecomputer/pierre6.3k—~608Automated safety check: PassApache-2.0
Ha Frontend Testinghome-assistant/frontend5.7k—~1.7kAutomated safety check: PassApache-2.0

Similar skills

  • Acceptance Test Authoring

    intent-driven-dev/intent-driven-template

    A skill your agent uses when creating or modifying acceptance tests, configuring cucumber-js or behave runners, writing or refactoring step definitions, linting executable Gherkin specs, choosing an…

    161 GitHub stars~2k tokensUpdated 5 days ago
    Testing & QAAuto-check passed
  • Odc Debugging

    DouglasNeuroInformatics/OpenDataCapture

    What actually breaks in Open Data Capture — a failing build, lint, unit test or e2e run; a change with no visible effect; a suite that stays green after you broke the code on purpose; an error…

    119 GitHub stars~2.8k tokensUpdated yesterday
    Testing & QAAuto-check: notes
  • Setup Codebase Harness

    AI-Builder-Club/skills

    Master skill — set up the full agent harness for any repo so an agent can work it reliably: legible (map-not-manual docs + custom lints), executable (one-command dev stack), verifiable (e2e gate + a…

    1.3k GitHub stars~1.4k tokensUpdated 23 days ago
    Testing & QAAuto-check passed
  • Chooses the right verification step after a code change in Pierre's monorepo: format and lint, a typecheck, Bun unit tests, snapshots, or Playwright E2E.

    6.3k GitHub stars~608 tokensUpdated today
    Testing & QAAuto-check passed
  • Ha Frontend Testing

    home-assistant/frontend

    Home Assistant frontend testing and validation workflow. An agent skill from home-assistant/frontend.

    5.7k GitHub stars~1.7k tokensUpdated today
    Testing & QAAuto-check passed
  • Precommit

    ploxc/modbux

    Run the checklist before committing or merging — read the diff, lint, typecheck, the unit suite, the e2e specs the change touches, then report and commit.

    110 GitHub stars~1.5k tokensUpdated today
    Testing & QAAuto-check passed

More from jh941213/my-cc-harness

All 62 skills in this repo
  • API Design Principles

    jh941213/my-cc-harness

    REST 및 GraphQL API 설계 원칙 가이드. An agent skill from jh941213/my-cc-harness.

    126 GitHub starsUsed in 18 repos~3.4k tokens
    Auto-check passed
  • Tailwind Design System

    jh941213/my-cc-harness

    Build scalable design systems with Tailwind CSS, design tokens, component libraries, and responsive patterns.

    126 GitHub starsUsed in 10 repos~4.7k tokens
    Auto-check passed
  • Docs Architecture

    jh941213/my-cc-harness

    Generate/update architecture docs — ARCHITECTURE.md (codemap), architecture diagrams (C4 mermaid), ADRs (MADR), data model ERD.

    126 GitHub stars~923 tokensUpdated 2 mo ago
    Auto-check: notes
  • Auto Memory

    jh941213/my-cc-harness

    A skill your agent uses when starting substantial work in a repo (implementation, fixes, deploys, debugging), when first exploring a new repo, or when finishing work that produced reusable knowledge.

    126 GitHub stars~890 tokensUpdated 2 mo ago
    Auto-check passed
  • Async Python Patterns

    jh941213/my-cc-harness

    Python asyncio 및 async/await 패턴 가이드. An agent skill from jh941213/my-cc-harness.

    126 GitHub starsUsed in 14 repos~4.7k tokens
    Auto-check passed
  • Python Testing Patterns

    jh941213/my-cc-harness

    Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development.

    126 GitHub starsUsed in 17 repos~5.4k tokens
    Auto-check passed

Questions about Verify

What does Verify do?

Code verification after task completion (typecheck, lint, test, build). Verify is an agent skill from jh941213/my-cc-harness. Code verification after task completion (typecheck, lint, test, build).

When should I use Verify?

Verify fits situations like: tasks that involve Linting and formatting; tasks that involve End-to-end testing.

How do I install Verify in Claude Code?

Run `npx skills add jh941213/my-cc-harness --skill verify -a claude-code`. Or copy the skill folder (skills_en/verify in jh941213/my-cc-harness) into .claude/skills/verify in your project. Claude Code loads it when a task matches its description.

How do I install Verify in Codex?

Run `npx skills add jh941213/my-cc-harness --skill verify -a codex`. Or copy the skill folder (skills_en/verify in jh941213/my-cc-harness) into .agents/skills/verify in your project. Codex loads it when a task matches its description.

Can I use Verify 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 jh941213/my-cc-harness --skill verify -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, .gemini/skills/verify, .github/skills/verify and .opencode/skills/verify in your project.

What does Verify need to run?

Going by SKILL.md and its folder, Verify needs the command-line tools its instructions call (npx, go, cargo, ruff, pytest and npm). Our summary lists: Python 3; Node.js. Its frontmatter pre-approves these tools: Read, Bash, Grep, Edit.

Does Verify access the network?

SKILL.md contains no URLs. Its commands use npx and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Verify safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Verify use?

No licence was found for Verify or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Verify use?

About 1.1k tokens (SKILL.md is roughly 4.3k 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?

Skills that share tags, products or a category with Verify: Acceptance Test Authoring (intent-driven-dev/intent-driven-template, 161 stars), Odc Debugging (DouglasNeuroInformatics/OpenDataCapture, 119 stars), Setup Codebase Harness (AI-Builder-Club/skills, 1.3k stars) and Pierre Testing and Verification Guide (pierrecomputer/pierre, 6.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verify?

jh941213 (a GitHub user) maintains it in jh941213/my-cc-harness, which has 126 GitHub stars. The repository holds 62 skills in this directory. The repository was last updated on August 3, 2026.

Source: jh941213/my-cc-harness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.