Agent skill

Dev Verify

by classmethod in classmethod/tsumiki

This skill should be used when the user asks to "dev-verify", "実装の検証", "完了チェック", "verify implementation", "全テスト実行", "run all tests", "dev-verify auth".

MITAuto-check passedDevelopment

Install Dev Verify

skills CLI
$ npx skills add classmethod/tsumiki --skill dev-verify -a claude-code

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

GitHub CLI
$ gh skill install classmethod/tsumiki dev-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/classmethod/tsumiki.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/dev-verify .claude/skills/dev-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
dev-verify
GitHub stars
974
Token cost
~848 tokens
SKILL.md length
139 words
Files
1
Skills in repo
14
Repo updated
First seen
Licence
MIT

At a glance

This skill should be used when the user asks to "dev-verify", "実装の検証", "完了チェック", "verify implementation", "全テスト実行", "run all tests", "dev-verify auth".

  • Works in 9 steps: タスク完了チェック → 全テスト実行 → カバレッジチェック → …
  • Asks to dev-verify
  • SKILL.md covers 前提知識, ワークフロー and ルール・制約
  • Calls git and docker

What it does

Dev Verify is an agent skill from classmethod/tsumiki. This skill should be used when the user asks to "dev-verify", "実装の検証", "完了チェック", "verify implementation", "全テスト実行", "run all tests", "dev-verify auth". Plan単位で全タスクの完了状態とテスト・ビルド・Lintの整合性を検証し、レポートを出力する。

Its SKILL.md is about 850 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 Development, covering Linting and formatting. It works with Docker. The licence is MIT.

When your agent uses it

  • Asks to dev-verify
  • Verify implementation
  • Dev-verify auth

Example prompts

  • “dev-verify”
  • “完了チェック”
  • “verify implementation”
  • “/dev-verify”

Requirements

  • Docker

Workflow steps

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

  1. タスク完了チェック
  2. 全テスト実行
  3. カバレッジチェック
  4. ビルド確認
  5. Lint実行
  6. ファイルサイズチェック(500行ルール)
  7. 信号機サマリー
  8. レポート出力
  9. Docker クリーンアップ

What it can do on your machine

Read from SKILL.md and the folder at commit fa5aaff. 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:

    • git
    • docker

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

  • Network

    No URLs in SKILL.md. Its commands use git and docker, 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

Dev Verify loads about 848 tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 139 words of instructions outside code blocks.

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

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

The full file from classmethod/tsumiki at commit fa5aaff, republished under its MIT licence (© classmethod). 139 words, ~848 tokens.

Download SKILL.mdSave it as .claude/skills/dev-verify/SKILL.md (or your agent's skills folder).
name
dev-verify
description
This skill should be used when the user asks to "dev-verify", "実装の検証", "完了チェック", "verify implementation", "全テスト実行", "run all tests", "dev-verify auth". Plan単位で全タスクの完了状態とテスト・ビルド・Lintの整合性を検証し、レポートを出力する。
argument-hint
<plan-name>

Dev Verify

Plan単位ですべてのタスクの完了状態を確認し、全テスト実行・ビルド・Lint・ファイルサイズチェックを行い、検証レポートを docs/dev/plans/<plan-name>/reports/ に出力する。

前提知識

dev-*スキルフロー内の位置
dev-context → dev-plan → dev-impl → [dev-verify]
                                ↘ dev-debug
引数フォーマット
/dev-verify <plan-name>

ワークフロー

Step 1: タスク完了チェック

docs/dev/plans/<plan-name>/tasks/ 内の全タスクファイルを読み込み、フロントマターの status を確認する。

  • すべて done → Step 2 へ進む
  • pending / in_progress のタスクがある → ユーザーに未完了タスクの一覧を報告し、続行するか確認する(AskUserQuestion)
Step 2: 全テスト実行

docs/dev/context.md からテスト実行コマンドを取得し、全テストを実行する。

bash
# context.md の Test Framework セクションからコマンドを取得
<test-command>

テスト結果を記録する: passed / failed / skipped の件数。

Step 3: カバレッジチェック

docs/dev/context.md の Test Framework セクションから Coverage Command と Coverage Threshold を取得し、プロジェクト全体のカバレッジを計測する。

  1. Coverage Command でプロジェクト全体のカバレッジを計測する
  2. パッケージごとにカバレッジ率を抽出し、閾値と比較する
  3. [no test files] は 0% として扱う
  4. 閾値未達のパッケージは Issues Found に記録する
Step 4: ビルド確認

コンパイル言語やビルドステップがある場合、ビルドコマンドを実行する(context.md から取得)。

インタープリタ言語でビルドステップがない場合はスキップする。

Step 5: Lint実行

context.md に Lint コマンドが記載されている場合、実行する。記載がない場合はスキップする。

Step 6: ファイルサイズチェック(500行ルール)

Planで変更・作成されたファイル(各タスクファイルの Files セクションから収集)の行数を確認する(絶対パスを使用):

bash
wc -l "$(git rev-parse --show-toplevel)/<ファイルの相対パス>"

500行を超えるファイルがあれば警告として記録する。

Step 7: 信号機サマリー

Plan内の全タスクの確信度レポートを集約する:

  • 🟡 妥当な推測の項目一覧(ユーザー確認推奨)
  • 🔴 AI推論補完の項目一覧(人間の確認必須)

🔴 が残っている場合は明確に警告する。

Step 8: レポート出力

検証結果を docs/dev/plans/<plan-name>/reports/verify-YYYY-MM-DD.md に出力する。

markdown
# Verification Report - YYYY-MM-DD
## Plan: <plan-name>

## Summary

| Item | Result |
|------|--------|
| Tasks | X/Y completed |
| Tests | Z passed, W failed, V skipped |
| Coverage | X/Y packages above threshold (threshold: 80%) |
| Build | OK / NG / N/A |
| Lint | OK / NG / N/A |
| 500-line rule | OK / X files over limit |

## Task Status

| ID | Title | Status |
|----|-------|--------|
| 001 | ... | done |
| 002 | ... | done |

## Test Results

[テスト実行の出力サマリー]
[失敗テストがある場合は詳細]

## Coverage Results

| パッケージ | カバレッジ | 閾値 | 結果 |
|-----------|----------|------|------|
| internal/handler | XX.X% | 80% | OK / NG |

[閾値未達パッケージの詳細(ある場合)]

## File Size Check

[500行超過ファイルの一覧(ある場合)]

## Confidence Summary

### 🟡 妥当な推測(要確認)
- [ファイル](パス) — [確認すべき点]

### 🔴 AI推論補完(人間の確認必須)
- [ファイル](パス) — [判断が必要な理由]

## Issues Found

[検出された問題の詳細]

## Recommendations

[問題がある場合の次アクション提案]
- テスト失敗 → `/dev-debug` の使用を推奨
- 500行超過 → `/dev-impl` のリファクタリングを推奨
- 🔴 残存 → 該当ファイルの人間レビューを推奨
Step 9: Docker クリーンアップ

プロジェクトルートに docker-compose.yml または docker-compose.yaml が存在するか確認する。存在する場合:

  1. docker compose down を実行してコンテナを停止する
  2. 停止に失敗した場合はユーザーに報告する(ブロッキングにしない)

ルール・制約

  • context.md が存在しない場合、テスト・ビルド・Lintコマンドが不明であることを報告し、可能な範囲で検証する
  • テスト失敗がある場合でもレポートは出力する(中断しない)
  • レポートファイルが既存の場合は日付が異なれば新規ファイルとして作成し、同日であれば上書きする
  • テスト実行はサブエージェントではなく直接 Bash で実行する(結果の全文がレポートに必要)
  • カバレッジ閾値未達のパッケージがある場合は VERIFY_ISSUES_FOUND とする
  • Lint/ビルドコマンドが context.md にない場合はスキップし、レポートに N/A と記載する
  • Bash コマンドはプロジェクトルートの 絶対パス を使用する($(git rev-parse --show-toplevel) でルートを取得)

© classmethod, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/dev-verify of classmethod/tsumiki.

Open the folder on GitHubat commit fa5aaff

Compare with similar skills

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

Dev Verify compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Dev Verify this skillclassmethod/tsumiki974—~848Automated safety check: PassMIT
Golang Continuous Integrationsamber/cc-skills-golang3.4k—~3.7kAutomated safety check: PassMIT
Debug CIweb-infra-dev/rslint460—~2.8kAutomated safety check: PassMIT
Kouchou AI Developmentdigitaldemocracy2030/kouchou-ai171—~540Automated safety check: NotesAGPL-3.0
Verifygocronx-team/gocron808—~529Automated safety check: PassMIT
Maintainer Testing ReleaseVectorSpaceLab/AREX-Skill328—~697Automated safety check: PassAGPL-3.0

Similar skills

  • Golang Continuous Integration

    samber/cc-skills-golang

    GitHub Actions CI/CD pipeline configuration for Golang projects — workflow files for test, lint, SAST, coverage and vulnerability-scan jobs, Dependabot and Renovate config files, GoReleaser release…

    3.4k GitHub stars~3.7k tokensUpdated 6 days ago
    DevelopmentAuto-check passed
  • Debug CI

    web-infra-dev/rslint

    Reproduce Linux CI failures locally using Docker when the same tests pass on the host, especially Go platform differences and VS Code extension tests requiring xvfb.

    460 GitHub stars~2.8k tokensUpdated today
    DevelopmentAuto-check passed
  • Kouchou AI Development

    digitaldemocracy2030/kouchou-ai

    Local development setup, build and lint commands, environment configuration, and deployment helpers for the kouchou-ai repo.

    171 GitHub stars~540 tokensUpdated today
    DevelopmentAuto-check: notes
  • Verify

    gocronx-team/gocron

    Reproduce the complete gocron CI pipeline locally and report every result.

    808 GitHub stars~529 tokensUpdated 5 days ago
    DevelopmentAuto-check passed
  • Maintainer Testing Release

    VectorSpaceLab/AREX-Skill

    Use this quip-miner sub-skill for maintainer pytest selection, CI invariants, no-inline-sampling lint, multiprocessing/hang debugging, versioning, Docker/PyInstaller release checks, and safe…

    328 GitHub stars~697 tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Megalinter Check

    nvuillam/npm-groovy-lint

    Collect MegaLinter lint errors for the current repository. An agent skill from nvuillam/npm-groovy-lint.

    248 GitHub starsUsed in 1 repo~3.9k tokens
    DevOps & CloudAuto-check: notes

More from classmethod/tsumiki

All 14 skills in this repo
  • Dev Context

    classmethod/tsumiki

    This skill should be used when the user asks to "dev-context", "プロジェクトコンテキストを生成", "プロジェクトを分析", "generate project context", "analyze project", "コンテキストを更新".

    974 GitHub stars~755 tokensUpdated 2 mo ago
    Auto-check passed
  • Dev Impl

    classmethod/tsumiki

    This skill should be used when the user asks to "dev-impl", "タスクを実装", "テストファースト実装", "implement task", "実装を開始", "クイック修正", "quick fix", "dev-impl auth 001".

    974 GitHub stars~1.3k tokensUpdated 2 mo ago
    Auto-check passed
  • Dev Plan

    classmethod/tsumiki

    This skill should be used when the user asks to "dev-plan", "実装計画を作成", "要件からタスク分解", "create implementation plan", "plan tasks", "タスクを分割", "設計してタスクにする", "詳細要件定義", "full-spec plan", "EARS要件".

    974 GitHub stars~2.5k tokensUpdated 2 mo ago
    Auto-check passed
  • Dev Run

    classmethod/tsumiki

    This skill should be used when the user asks to "dev-run", "自動実装", "タスクを一括実装", "auto implement", "run all tasks", "タスクを自動実行", "バッチ実装", "dev-run auth 001 005".

    974 GitHub stars~1.8k tokensUpdated 2 mo ago
    Auto-check passed
  • Dev Screen Spec

    classmethod/tsumiki

    This skill should be used when the user asks to "dev-screen-spec", "画面仕様を生成", "画面仕様を更新", "screen spec", "generate screen spec", "update screen spec", "画面仕様ドキュメント".

    974 GitHub stars~4.2k tokensUpdated 2 mo ago
    Auto-check passed
  • Dev Webtest

    classmethod/tsumiki

    This skill should be used when the user asks to "dev-webtest", "Webテスト", "画面の動作確認", "E2Eテスト", "web test", "visual check", "モンキーテスト", "アクセシビリティチェック", "レスポンシブテスト", "フォームテスト".

    974 GitHub stars~4.2k tokensUpdated 2 mo ago
    Auto-check passed

Works with

Questions about Dev Verify

What does Dev Verify do?

This skill should be used when the user asks to "dev-verify", "実装の検証", "完了チェック", "verify implementation", "全テスト実行", "run all tests", "dev-verify auth". Dev Verify is an agent skill from classmethod/tsumiki. This skill should be used when the user asks to "dev-verify", "実装の検証", "完了チェック", "verify implementation", "全テスト実行", "run all tests", "dev-verify auth".

When should I use Dev Verify?

Dev Verify fits situations like: asks to dev-verify; verify implementation; dev-verify auth.

How do I install Dev Verify in Claude Code?

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

How do I install Dev Verify in Codex?

Run `npx skills add classmethod/tsumiki --skill dev-verify -a codex`. Or copy the skill folder (skills/dev-verify in classmethod/tsumiki) into .agents/skills/dev-verify in your project. Codex loads it when a task matches its description.

Can I use Dev 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 classmethod/tsumiki --skill dev-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/dev-verify, .gemini/skills/dev-verify, .github/skills/dev-verify and .opencode/skills/dev-verify in your project.

What does Dev Verify need to run?

Going by SKILL.md and its folder, Dev Verify needs the command-line tools its instructions call (git and docker). Our summary lists: Docker.

Does Dev Verify access the network?

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

Is Dev Verify 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 Dev Verify use?

Dev Verify is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Dev Verify use?

About 848 tokens (SKILL.md is roughly 3.4k 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 Dev Verify?

Skills that share tags, products or a category with Dev Verify: Golang Continuous Integration (samber/cc-skills-golang, 3.4k stars), Debug CI (web-infra-dev/rslint, 460 stars), Kouchou AI Development (digitaldemocracy2030/kouchou-ai, 171 stars) and Verify (gocronx-team/gocron, 808 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dev Verify?

classmethod (a GitHub organization) maintains it in classmethod/tsumiki, which has 974 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on August 7, 2026.

Source: classmethod/tsumiki on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.