Skip to content
Skills Library
Programming · Review & audit

verification-loop

/verification-loop

A comprehensive verification system for Nemo Code sessions. Use when verifying a Nemo Code session's work before claiming it is complete.

Repository
Nemo-Cli ↗
Licence
Apache-2.0
Last repository change
05.11.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 05.11.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

A comprehensive verification system for Nemo Code sessions. Use when verifying a Nemo Code session's work before claiming it is complete.

Original author description

A comprehensive verification system for Nemo Code sessions. Use when verifying a Nemo Code session's work before claiming it is complete.

How it works

  1. When to Use
  2. Verification Phases
  3. Output Format
  4. Continuous Mode
  5. Integration with Hooks
Original SKILL.md headings · 133 lines, 382 words
SKILL.md preview
---
name: verification-loop
description: "A comprehensive verification system for Nemo Code sessions. Use when verifying a Nemo Code session's work before claiming it is complete."
license: MIT
metadata:
  origin: ECC
---

# Verification Loop Skill

A comprehensive verification system for Nemo Code sessions.

## When to Use

Invoke this skill:

- After completing a feature or significant code change
- Before creating a PR
- When you want to ensure quality gates pass
- After refactoring

## Verification Phases

### Phase 1: Build Verification

```bash
# Check if project builds
npm run build 2>&1 | tail -20
# OR
pnpm build 2>&1 | tail -20
```

If build fails, STOP and fix before continuing.

### Phase 2: Type Check

```bash
set -o pipefail
# TypeScript projects
npx --no-install tsc --noEmit 2>&1 | head -30

# Python projects
pyright . 2>&1 | head -30
```

Report all type errors. Fix critical ones before continuing.

### Phase 3: Lint Check

```bash
# JavaScript/TypeScript
npm run lint 2>&1 | head -30

# Python
ruff check . 2>&1 | head -30
```

### Phase 4: Test Suite

```bash
# Run tests with coverage
npm run test -- --coverage 2>&1 | tail -50

# Check coverage threshold
# Target: 80% minimum
```

Report:

- Total tests: X
- Passed: X
- Failed: X
- Coverage: X%

### Phase 5: Security Scan

```bash
# Check for secrets
grep -rn "sk-" --include="*.ts" --include="*.js" . 2>/dev/null | head -10
grep -rn "api_key" --include="*.ts" --include="*.js" . 2>/dev/null | head -10

# Check for console.log
grep -rn "console.log" --include="*.ts" --include="*.tsx" src/ 2>/dev/null | head -10
```

### Phase 6: Diff Review

```bash
# Show what changed
git diff --stat
git diff HEAD~1 --name-only
```

Review each changed file for:

- Unintended changes
- Missing error handling
- Potential edge cases

## Output Format

After running all phases, produce a verification report:

```
VERIFICATION REPORT
==================

Build:     [PASS/FAIL]
Types:     [PASS/FAIL] (X errors)
Lint:      [PASS/FAIL] (X warnings)
Tests:     [PASS/FAIL] (X/Y passed, Z% coverage)
Security:  [PASS/FAIL] (X issues)
Diff:      [X files changed]

Overall:   [READY/NOT READY] for PR

Issues to Fix:
1. ...
2. ...
```

## Continuous Mode

For long sessions, run verification every 15 minutes or after major changes:

```markdown
Set a mental checkpoint:

- After completing each function
- After finishing a component
- Before moving to next task

Run: /verify
```

## Integration with Hooks

This skill complements PostToolUse hooks but provides deeper verification.
Hooks catch issues immediately; this skill provides comprehensive review.

Versions

RepositoryScoreLicence
This page · SHRIJANAGAIN/Nemo-Cli100Apache-2.0
frankxai/claude-skills-library100MIT
smartworldarafath/REA_Skill100MIT
MJayConstantino/skills100MIT
affaan-m/ECC100MIT
affaan-m/ECC100MIT
Galaxy-Dawn/claude-scholar100MIT
nguyentrunghieutcu/ctxora-engine100MIT
materialofair/oh-my-codex100MIT

Database snapshot: 13.11.2026 · package version fc993fee3aa6 (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

  • 95nemojs-skill
    Generates Nemo.js automation tests in JavaScript. PayPal's Selenium-based test framework for Node.js. Use when user mentions "Nemo.js", "nemo automation". Triggers on: "Nemo.js", "nemo automation", "nemo test", "PayPal test framework".
  • 100ck
    Persistent per-project memory for Nemo Code. Auto-loads project context on session start, tracks sessions with git activity, and writes to native memory. Commands run deterministic Node.js scripts — behavior is consistent across model versions. Use when a project needs context…
  • 96python-tests
    Python tests for NeMo Fabric; use this when writing tests
  • 100codebase-onboarding
    Analyze an unfamiliar codebase and generate a structured onboarding guide with architecture map, key entry points, conventions, and a starter NEMO.md. Use when joining a new project or setting up Nemo Code for the first time in a repo.
  • 100test-go-binding
    Build and test the NeMo Relay Go binding; use this for go/nemo_relay changes or Go-facing integration checks
  • 100verification-before-completion
    Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Feedback and reports

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