
ns-judge
(NS) Delivery proof after Code Review: Approved. AC tokens, spec-coverage ledger, ui-contract testid/copy, visual checklist vs repo. Approved only at score 10; score 9 = Rejected. Use at version closure, GitLab issue delivery, or ad-hoc after reviewer Approved — even without naming this skill. Do NOT run before Code Review: Approved. Do NOT replace ns-reviewer SOLID/security. Do NOT write product code.
- Installs
- 65
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/nextstage-brasil/skills --skill ns-judge- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads ns-judge automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Delivery Judge
Proof that shipped diff matches input ACs. Not SOLID. Not security. Code quality already passed ns-reviewer.
Shape (not a vendor copy): the-judge SKILL.md v1.4.0. Reimplement here. Do not paste that file. No GitHub APPROVE, emoji, banned-word gate, six LLM passes, post_review.py.
When
Parent already holds Code Review: Approved from ns-reviewer / reviewer-agent. Same parent then reads this SKILL.md in-session. No judge-agent in v1. Human /ns-judge = session face only.
| Parent | Mode | AC source |
|---|---|---|
run-implementation Step 5 | closure | sdd/requirements.md |
ns-autonomous standalone close | closure | same |
ns-coder ad-hoc / C2 | adhoc | --requirements / --ac-file if present; else skip AC proof |
ns-execution-gitlab-issue Phase 4 | issue | --ac-file from synthesis (Python never calls GitLab) |
ns-reviewer MUST NOT dispatch this skill.
No Code Review: Approved → stop. Do not judge. Tell parent run reviewer first.
Session boot
See ../../ns-harness/references/session-boot.md. Cold start this judge run: Session boot 1–6 before probe. Never tool-Read AGENTS.md.
Probe (Python optional)
command -v python3. Missing or any script exit 1 → preflight skipped. Residual LLM still runs. Never Blocked because Python absent.
Details + CLI: references/workflow.md. Token regex lives in scripts/prove_ac.py only — not this body.
Workflow
- Confirm last code verdict is
Code Review: Approved. Else stop. - Probe Python. If present:
prove_ac.pyfor active modegit diff \| python3 scripts/scan_bypasses.py(always exit 0)
prove_ac.pyexit 2 → format fix map (../ns-reviewer/references/review-fix-map.template.md), last lineDelivery Review: Rejected. No residual LLM.- Residual LLM (scripts skipped or prove exit 0): leftover that tests did not already catch. Do not restate phpunit/lint. Naked suppressions from
scan_bypasses.py= judge in residual. Claim needs evidence (Pass E, stricter: AC tokens). - Write
findings.json. Runreview_gate.py. Gate fail → edit JSON, re-run. Not productBlocked. - Last line:
Delivery Review: {Approved|Rejected|Blocked}. Score in Executive Summary.
Score gate (same table as ns-reviewer)
Copy. Do not invent second rubric. Approved = zero Criticals and score = 10. Score 9 = Rejected (Lift).
| Score | Meaning | Verdict impact |
|---|---|---|
| 10 | Ship as-is | Approved (only eligible score) |
| 9 | Near-bar leftover on AC/ledger/ui-contract item | Rejected — Lift |
| ≤8 | Below bar / missing AC token / unmet ledger | Rejected |
Approved only when all true:
- Zero Critical findings
- Overall score = 10/10
- Every scored AC token hit in repo (when AC source present)
Missing AC token / unmet ledger / missing testid → Critical or cap ≤8 → cannot be 10.
Skip-Python residual: same 10-only rule. LLM still emits score + verdict.
review_gate.py rejects JSON that claims Approved with score ≠ 10 or with P0 findings.
Modes
closure
prove_ac.py --mode closure [--repo .] [--version VERSION_SAN] [--requirements PATH]
Law: #### Acceptance criteria: checkbox lines. Tokens: backticks, quoted strings, data-testid, HTTP \b[1-5][0-9]{2}\b (in script). ≥1 token and zero repo hits → P0 Rejected. Zero tokens on a line → unscored (residual). Script does not claim the feature works.
Also: ledger missing / unmapped; ui-contract testid/copy; visual checklist literals. Same Rejected bar.
issue
--mode issue --ac-file PATH. Synthesis file. No GitLab in Python.
adhoc
Skip AC proof unless --requirements or --ac-file. Residual still runs. Parent report may mark AC proof n/a.
Required output
Approved
Executive Summary
- Score 10
- One sentence vs rubric
- Two-line assessment
- AC proof:
pass|n/a(adhoc, no source)
Then: Delivery Review: Approved
Rejected / Blocked
Executive Summary
- Score 1–10
- One sentence
- Two-line assessment
Fix map (agent)
../ns-reviewer/references/review-fix-map.template.md
Then: Delivery Review: Rejected or Delivery Review: Blocked
Constraints
- Read-only on product files
- No dispatch from
ns-reviewer - No GitHub review API
- Findings need
evidence: [{type:internal,ref:path:line}]for P0/P1 - Residual does not restate what tests already catch
References
| File | When |
|---|---|
references/workflow.md | Probe, skip, CLI, findings.json |
../ns-reviewer/references/review-gate-workflow.md | Parent sequence (code then judge) |
../ns-reviewer/references/review-fix-map.template.md | Rejected body |
scripts/prove_ac.py | AC / ledger / ui-contract / visual law |
scripts/scan_bypasses.py | Diff stdin candidates |
scripts/review_gate.py | findings.json gate |
FAQ
What does the ns-judge skill do?
(NS) Delivery proof after Code Review: Approved. AC tokens, spec-coverage ledger, ui-contract testid/copy, visual checklist vs repo. Approved only at score 10; score 9 = Rejected. Use at version closure, GitLab issue delivery, or ad-hoc after reviewer Approved — even without naming this skill. Do NOT run before Code Review: Approved. Do NOT replace ns-reviewer SOLID/security. Do NOT write product code.
How do I install ns-judge?
Run npx skills add https://github.com/nextstage-brasil/skills --skill ns-judge in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/ns-judge/ (personal) or .claude/skills/ns-judge/ (project).
Which AI agents can use ns-judge?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is ns-judge safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains ns-judge?
It is published by nextstage-brasil in nextstage-brasil/skills. It has 65 recorded installs.
More from nextstage-brasil/skills
ns-gitlab-board-sync
nextstage-brasil/skills
(NS) Sync existing GitLab issues with local planning/execution — milestone, RF labels, status, assignee, estimates, spent time. Use during implementation when tasks link to GitLab issues or after plan-version-from-gitlab sync — not for creating new issues (use mcp-gitlab-usage). Always atomic setissuelabels and three-step status cycle.
ns-spec-driven
nextstage-brasil/skills
Open the skill to read its SKILL.md instructions.
ns-gitlab-ci-generator
nextstage-brasil/skills
Open the skill to read its SKILL.md instructions.
ns-project-manager
nextstage-brasil/skills
(NS) Gated PM: clarify, RICE/WSJF, sprint, PERT/Monte Carlo; PRD (product discovery doc); product/project roadmap (multi-version); version handoff; release delivery report for leadership (relatório de entrega da versão, deploy report para diretoria, o que vai para produção); risk/status/OKR; orçamento, Function Points, proposta comercial, preço do ponto de função, quanto custa o PF; cronograma P100/P85/P50. Use on transcripts, backlog, timeline, delivery date, status, roadmap, roadmap do projeto, roadmap de produto, PRD, product requirements document, documento de requisitos de produto, versões entregues/planejadas, orçamento, cotação, cronograma, handoff, fecha a versão, valor do PF, não sei o preço do ponto de função, dúvidas do dev, perguntas da equipe sobre o PRD — even if PM unnamed. Do NOT use for coding, SDD requirements.md, GitLab issue execution, or /ns-requirements-enricher.
mcp-gitlab-usage
nextstage-brasil/skills
Open the skill to read its SKILL.md instructions.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.