Skip to content
Skills Library
Programming · Testing

verify

/verify

Use this skill to run deterministic project verification (build, types, lint, tests, security, git status) with mode-based command sets.

Repository
oh-my-codex ↗
Licence
MIT
Last repository change
22.08.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 22.08.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use this skill to run deterministic project verification (build, types, lint, tests, security, git status) with mode-based command sets.

Original author description

Use this skill to run deterministic project verification (build, types, lint, tests, security, git status) with mode-based command sets.

How it works

  1. Capabilities
  2. Input Requirements
  3. How to Use
  4. Mode Matrix
  5. Verification Order
  6. Output Format
Original SKILL.md headings · 92 lines, 271 words
SKILL.md preview
---
name: verify
description: Use this skill to run deterministic project verification (build, types, lint, tests, security, git status) with mode-based command sets.
version: 0.3.0
source: fork
checksum: b1daa6b6d105b8e325f541119e3d9a523f709b16a650702e9f4e5cfd93f3f011
updated_at: 2026-03-12T18:57:03+08:00
intent: verification
layer: foundation
---


# Verify Skill

> Codex invocation: use `$verify [mode]` or `verify: [mode]`

Run comprehensive verification on current codebase state.

## Capabilities

- Standardized verification order.
- Mode-specific command subsets (`quick`, `full`, `pre-commit`, `pre-pr`).
- Security and debug-log audits.
- Clear pass/fail report with blockers.

## Input Requirements

- `mode` (optional): `quick` | `full` | `pre-commit` | `pre-pr`.
- default mode: `full`.

## How to Use

```text
$verify
$verify quick
$verify pre-commit
$verify pre-pr
```

## Mode Matrix

1. `quick`: build + typecheck
2. `full`: build + typecheck + lint + tests + logs + git status
3. `pre-commit`: typecheck + lint + targeted tests + git status
4. `pre-pr`: full + security scan

## Verification Order

1. **Build Check**
- Run project build command.
- If it fails, report and stop.

2. **Type Check**
- Run type checker (`tsc --noEmit` / equivalent).

3. **Lint Check**
- Run lint command.

4. **Test Suite**
- If implementation files changed, run `omcodex test changed` first.
- Run tests (targeted first, then broader if needed).
- Report pass/fail counts and coverage if available.

5. **Security Scan** (`pre-pr` + `full` recommended)

```bash
rg -n "sk-[A-Za-z0-9_-]{20,}" --glob '!node_modules' .
rg -n "api[_-]?key|secret|token\s*=\s*['\"]" --glob '!node_modules' .
```

6. **Console Log Audit**

```bash
rg -n "console\.log|print\(" src tests
```

7. **Git Status**

```bash
git status --short
git diff --name-only
```

## Output Format

```text
VERIFICATION: [PASS/FAIL]

Mode:     [quick/full/pre-commit/pre-pr]
Build:    [OK/FAIL]
Types:    [OK/X errors]
Lint:     [OK/X issues]
Tests:    [X/Y passed, Z% coverage or N/A]
Security: [OK/X findings]
Logs:     [OK/X console logs]
Git:      [clean/dirty]

Ready for PR: [YES/NO]
```

If failed, include blocker list ordered by severity and recommended next commands.

Versions

RepositoryScoreLicence
This page · materialofair/oh-my-codex100MIT
yonatangross/orchestkit100MIT
yonatangross/orchestkit100MIT
NolwennD/gabier100Apache-2.0
ericrisco/rsc-harness100MIT
sentimony/agentic-workflow100MIT
JoDi-27/JoDi-SDD100MIT
marcel-bich/marcel-bich-claude-marketplace100MIT
kdlbs/kandev100AGPL-3.0

Database snapshot: 13.11.2026 · package version 8fe548e1910f (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100verification-loop
    Run a six-phase verification of a Claude Code session's work — build, type check, lint, tests with coverage, security grep, and diff review — then produce a PASS/FAIL verification report. Use when verifying work after completing a feature or refactor, before creating a PR, or…
  • 95verification-loop
    Comprehensive 6-check verification framework for validating implementation quality across build, types, lint, tests, security, and diff review. This skill ensures code meets all quality gates before phase completion. Triggers on "verify implementation", "run verification",…
  • 90check
    Validate code quality — auto-fix formatting/lint, verify types, run tests. Use when asked to "validate code", "check code", or validate before committing; also lint-only asks ("run linter", "fix lint errors"). Don't use for committing (/commit), pushing (/to-pr), or writing new tests (/tdd).
  • 100run-tests
    Stage 4 (Test) - automatically run build, typecheck, lint and Vitest unit tests for the app on the feature branch, set them up if missing, map results to spec requirements and write test-report.md. Use after a build/PR, when the user says "run the tests", "verify this", "is it…
  • 100certify
    Full verification loop — tests, types, lint, build, and a Playwright browser check for UI projects; collects evidence before any success claim. Use to verify a change is actually green.
  • 100verification-loop
    Run a six-phase verification of a Claude Code session's work — build, type check, lint, tests with coverage, security grep, and diff review — then produce a PASS/FAIL verification report. Use when verifying work after completing a feature or refactor, before creating a PR, or…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.