home / skills / shotaiuchi / dotclaude / ghwf6-verify

ghwf6-verify skill

safe

This skill verifies implementation by running lint, type checks, build, tests, and code reviews against the spec to ensure correctness and quality.

npx playbooks add skill shotaiuchi/dotclaude --skill ghwf6-verify

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

1.3 KB

---
name: ghwf6-verify
description: 実装を検証
argument-hint: ""
context: fork
agent: general-purpose
---

**Always respond in Japanese. Write all workflow documents (*.md) in Japanese.**

# /ghwf6-verify

実装の検証を行う。

## Usage

```
/ghwf6-verify
```

## Prerequisites

- `ghwf5-implement` 完了済み
- 全実装ステップ完了

## Processing

### 1. Load Context

- Read `state.json` for active work
- Fetch Issue/PR with comments:
  ```bash
  gh issue view <issue> --json body,comments
  gh pr view <pr> --json comments,reviews
  ```

### 2. Run Verification

- Lint: `pnpm lint`
- Type check: `pnpm type-check`
- Build: `pnpm build`
- Test: `pnpm test`

### 3. Code Review

- Review implementation against spec
- Check for security issues
- Verify edge cases handled

### 4. Create/Update 06_VERIFY.md

- Test results
- Review findings
- Issues to address

### 5. Handle Issues

If issues found:
- Fix issues
- Re-run verification
- Update documentation

### 6. Commit & Push

**Execute immediately without confirmation:**

```bash
git add .
git commit -m "docs(wf): verify implementation <work-id>"
git push
```

### 7. Update PR & Labels

- PR チェックリスト更新
- `ghwf:step-6` ラベル追加

### 8. Update State

```json
{
  "current": "ghwf6-verify",
  "next": "ghwf7-pr",
  "last_execution": "<ISO8601>"
}
```

Overview

This skill verifies a completed implementation by running automated checks, performing a focused code review, and recording verification results. It coordinates test runs, build and lint checks, and updates project state and PR metadata to mark verification progress.

How this skill works

The skill loads the current work context from state.json and fetches the related issue or pull request details and comments. It runs a sequence of verification commands (lint, type-check, build, test), performs a manual review for spec compliance and security/edge cases, writes a verification report (06_VERIFY.md), and updates the repo and PR state before advancing the workflow.

When to use it

After completing all implementation steps and prerequisites (ghwf5-implement).
Before creating or finalizing a pull request merge.
When you need a formal verification record for the implementation.
When automated checks or tests must be validated together with manual review.

Best practices

Ensure state.json reflects the active work item before starting verification.
Run the exact verification commands locally or in CI: pnpm lint, pnpm type-check, pnpm build, pnpm test.
Document all test results, review findings, and remaining issues in 06_VERIFY.md.
Treat security checks and edge-case handling as first-class review items.
Commit and push verification updates immediately to keep PR state accurate.

Example use cases

Verify a feature branch before requesting final review and merge.
Re-run verification after fixes are applied to confirm resolution of reported issues.
Produce a verification artifact (06_VERIFY.md) to satisfy release or audit requirements.
Mark the workflow step complete and add labels so downstream automation continues.

FAQ

What commands are run during verification?

The sequence is pnpm lint, pnpm type-check, pnpm build, and pnpm test.

What happens if verification finds issues?

Fixes are applied, verification is re-run, documentation updated, and results committed and pushed.