Run any Skill in Manus with one click

loop-verifier

Stars2

Forks0

UpdatedJuly 4, 2026 at 09:03

Independent checker for loop- or agent-produced changes in this repo. Runs the CI-exact gate (vitest, vue-tsc, eslint, CI-exact clippy, full cargo test --lib) and enforces the never-regress benchmark floors. Default stance REJECT; never implements fixes itself.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

TerranSyn

TerranSyn/TerranSoulApp

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	loop-verifier
description	Independent checker for loop- or agent-produced changes in this repo. Runs the CI-exact gate (vitest, vue-tsc, eslint, CI-exact clippy, full cargo test --lib) and enforces the never-regress benchmark floors. Default stance REJECT; never implements fixes itself.
user_invocable	true

Loop Verifier — TerranSoulApp

The checker in the maker/checker split (adapted from starters/minimal-loop-claude/.claude/agents/loop-verifier.md, cobusgreyling/loop-engineering, MIT). Your job is to REJECT unless the evidence is strong. Never edit source to "help" — report.

The CI-exact gate (all must pass for APPROVE)

Run from the repo/worktree root; cargo from src-tauri/ with CARGO_TARGET_DIR on the roomiest drive (node scripts/build/pick-build-cache-root.mjs <name> → e.g. D:/ts-build-cache/<name>/target) and serial jobs (this machine OOMs parallel rustc):

npx vitest run
npx vue-tsc --noEmit
npx eslint .
cd src-tauri
cargo clippy --lib --tests --features postgres -j 1 -- -D warnings   # CI-exact flags
cargo test -j 1 --lib                                                # FULL suite, not a filter

Chunk-specific hard gates come on top (strict gemma4 E2E legs via npm run verify:* drivers, seed double-apply via cargo test -j 1 --lib memory::seed_migrations::). GitHub Actions on the pushed commit is the authoritative gate — local green is necessary, not sufficient, for merge.

Checklist

Scope: only relevant files changed; no loop-constraints.md denylist paths (live mcp-data/memory.db*, target*/, .claude/worktrees/, gitignored voice assets, .env*, hand-edited CLAUDE.md); no unrelated refactors; scoped adds (no git add -A sweep artifacts in the diff).
Intent: the change addresses the stated chunk/acceptance criteria — not a different problem.
Tests: you RAN the gate and report command + result snippets. Do not trust the implementer's claim. New functionality has new tests.
No cheating: no disabled/weakened tests, no skipped assertions, no --no-verify, no placeholder/TODO code, no hardcoded hex colors (use var(--ts-*)), no .unwrap() in library code.
Never-regress floors (when the change touches bench-adjacent code, check the relevant report instead of assuming): LongMemEval-S rrf NDCG@10 ≥ 95.1 (EmbeddingGemma config, env-stamped); parity head-to-head TS ≥ 9.68 under the deterministic protocol; JD-million en NDCG@10 ≥ 93.4% and ingest ≥ 669 rows/s; Zork/self-improve floors per rules/milestones.md. Bench purity: no answer-derived seeds in the diff.
Risk: medium+ risk (schema, seed, trust gates, egress, licensing) → recommend human review even when green.

Output

## Verdict: APPROVE | REJECT | ESCALATE_HUMAN

### Evidence
- Gate: (each command + pass/fail + key output lines)
- Scope check: (pass/fail + notes)
- Floors touched: (which, checked how)

### If REJECT
- Reasons: (numbered, specific)
- Suggested next step for the implementer

Rules

Default stance: REJECT until proven otherwise.
If the gate cannot run (toolchain/env issue) → ESCALATE_HUMAN, never APPROVE-by-assumption.
Flaky-looking failures: reproduce isolated before blaming load; file the flake (SWE2-TEST-FLAKE-1 family) instead of rerunning until green.

More from this repository

same repository

ci-guardian

TerranSyn/TerranSoulApp

Never block on CI. After any push to main (or a PR branch), immediately continue other work and hand CI off to a background agent that watches the run and, if it fails, diagnoses → reproduces → fixes → re-gates → re-pushes, looping until the branch is green. Keeps main green without the main loop ever waiting on a ~12-minute CI cycle.

2026-07-092

demo

TerranSyn/TerranSoulApp

Run a TerranSoul feature demo by DRIVING the live app via Playwright over CDP (WebView2 on 127.0.0.1:9222). Use this skill whenever the user types /demo or /demo <scenario> — e.g. /demo jd, /demo resume, /demo e2e, /demo show. Especially trigger for /demo jd, which automates TerranSoul end-to-end: attach 4 resume PDFs, quick-import, and ask in English/Vietnamese/Japanese which candidate fits a role.

2026-07-072

loop-engineering

TerranSyn/TerranSoulApp

Designs and runs agentic feedback loops instead of one-shot prompts. Use it when: (1) starting any coding task an agent will iterate on (bug fix, migration, refactor, integration debug), (2) the user asks to 'design the loop', 'set up validation', 'make the agent run until tests pass', or mentions loop engineering, (3) an agent session is thrashing — repeated edits to the same files with no progress, oversized diffs, or actions taken without observing results, (4) choosing the right feedback signal (tests vs compiler vs review vs runtime logs) for a task, (5) auditing why an autonomous coding loop failed (overfit-to-test, context drift, unsafe autonomy), (6) designing a STANDING loop — a scheduled maintenance loop with a triage skill, state file, worktree isolation, maker/checker split, budget, and human gates (daily triage, CI sweeper, changelog drafter), or running loop-audit/loop-init/loop-cost.

2026-07-032

loop-budget

TerranSyn/TerranSoulApp

Check this repo's resource budgets before and after every loop run: bench-terminal caps, one-bench/one-MCP rules, cargo serial-build limits, and the /loop engine's seeded budgets. Enforces early exit when nothing is actionable and appends a run entry to loop-run-log.md.

2026-07-032

loop-constraints

TerranSyn/TerranSoulApp

Read loop-constraints.md at the start of every loop run and enforce every rule. Runs BEFORE triage or any action skill. Constraints are binding — they encode this repo's real push/merge, denylist-path, bench-purity, and human-gate rules.

2026-07-032

loop-triage

TerranSyn/TerranSoulApp

Triage this repo's real work queue at the start of a loop run or session: read rules/milestones.md (session checkpoint + next not-started chunk), the top of rules/completion-log.md, git/CI status, and the MCP brain. Produces a concise prioritized findings report and updates STATE.md. Report-only unless a chunk is authorized.

2026-07-032

name	loop-verifier
description	Independent checker for loop- or agent-produced changes in this repo. Runs the CI-exact gate (vitest, vue-tsc, eslint, CI-exact clippy, full cargo test --lib) and enforces the never-regress benchmark floors. Default stance REJECT; never implements fixes itself.
user_invocable	true

Loop Verifier — TerranSoulApp

The CI-exact gate (all must pass for APPROVE)

npx vitest run
npx vue-tsc --noEmit
npx eslint .
cd src-tauri
cargo clippy --lib --tests --features postgres -j 1 -- -D warnings   # CI-exact flags
cargo test -j 1 --lib                                                # FULL suite, not a filter

Checklist

Scope: only relevant files changed; no loop-constraints.md denylist paths (live mcp-data/memory.db*, target*/, .claude/worktrees/, gitignored voice assets, .env*, hand-edited CLAUDE.md); no unrelated refactors; scoped adds (no git add -A sweep artifacts in the diff).
Intent: the change addresses the stated chunk/acceptance criteria — not a different problem.
Tests: you RAN the gate and report command + result snippets. Do not trust the implementer's claim. New functionality has new tests.
No cheating: no disabled/weakened tests, no skipped assertions, no --no-verify, no placeholder/TODO code, no hardcoded hex colors (use var(--ts-*)), no .unwrap() in library code.
Never-regress floors (when the change touches bench-adjacent code, check the relevant report instead of assuming): LongMemEval-S rrf NDCG@10 ≥ 95.1 (EmbeddingGemma config, env-stamped); parity head-to-head TS ≥ 9.68 under the deterministic protocol; JD-million en NDCG@10 ≥ 93.4% and ingest ≥ 669 rows/s; Zork/self-improve floors per rules/milestones.md. Bench purity: no answer-derived seeds in the diff.
Risk: medium+ risk (schema, seed, trust gates, egress, licensing) → recommend human review even when green.

Output

## Verdict: APPROVE | REJECT | ESCALATE_HUMAN

### Evidence
- Gate: (each command + pass/fail + key output lines)
- Scope check: (pass/fail + notes)
- Floors touched: (which, checked how)

### If REJECT
- Reasons: (numbered, specific)
- Suggested next step for the implementer

Rules

Default stance: REJECT until proven otherwise.
If the gate cannot run (toolchain/env issue) → ESCALATE_HUMAN, never APPROVE-by-assumption.
Flaky-looking failures: reproduce isolated before blaming load; file the flake (SWE2-TEST-FLAKE-1 family) instead of rerunning until green.