quality-gate
Skill1 starsChanged 7 months agoApache-2.0View on GitHub
Self-verification checklist for review outputs (WF1 Step 8). Primary script: scripts/run-quality-gate.py Usage: python3 run-quality-gate.py <working_dir> <deliverables_dir> <output_path> Run each check against the generated outputs. All must pass for clean delivery.
46 other projects use a version of this.
Adopted by
Most recently taken up by
- MarchTalk/ai-content-skillstheir own version, first seen Nov 16, 2026
- Fili999/ai-hubtheir own version, first seen Nov 15, 2026
- shimo4228/writingtheir own version, first seen Nov 15, 2026
- erraggy/oastoolstheir own version, first seen Nov 15, 2026
- shimo4228/zenn-contenttheir own version, first seen Nov 15, 2026
- jodyjdc/ultimate-best-seller-studiotheir own version, first seen Nov 8, 2026
Used with
Projects with it also use deploy.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
VercelSkilldeploy
Deploy applications to Vercel. Use when the user says "deploy", "deploy to Vercel", "push to production", "deploy my app", or "go live".
Also in 3 projects that use this
Other versions46 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 46
- RapierCraftStudios/ForgeDock★ 119same name
- microsoft/webui★ 102same name
- impecablemee/gtm-mcp★ 66same name
- microsoft/devsquad-copilot★ 50same name
- Romandredan/1c-quality-gate★ 50same name
- TerryFYL/ai-research-army★ 9same name
- Felpix-Studios/social-science-research★ 8same name
- BerryKuipers/claude-code-toolkit★ 7same name
- erraggy/oastools★ 7same name
- freskhu/genesis★ 5same name
36 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- citation-auditorSkill
- citation-checkerSkill
- cover-memo-writerSkill
- cross-document-checkerSkill
- document-parserSkill
- formatting-reviewerSkill
- ingestSkill
- known-issues-managerSkill
- library-managerSkill
- redline-generatorSkill
- scoring-engineSkill
- structure-checkerSkill
- substance-reviewerSkill
- writing-quality-reviewerSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 10 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 36 edited versions we read keep these.
10
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Run each check against the generated outputs.
- Distinctive: line 16
If a particular issue has no explicit textual correction, verify it is still represented by a comment in the redline DOCX
- Distinctive: line 20
Verify: No review comment in the redline DOCX itself contains a hallucination or unsupported assertion.
- Very specific: line 21
Read each comment → verify it is factually supportable from the document content or verification-audit.json
- Distinctive: line 29
No finding in the memo that doesn't exist in issue-registry
- Distinctive: line 30
No Critical/Major finding in issue-registry that's missing from the memo
- Distinctive: line 37
No mathematical errors in scoring
- Very specific: line 47
No citation in citation-list.json that's missing from verification-audit.json (at applicable depth)
- Distinctive: line 51
No Suggestion-level changes accepted in clean version
- Distinctive: line 52
No tracked changes remaining in clean DOCX
- Distinctive: line 63
If recommendation is "Pass" or "Pass with Warnings" → verify no Critical Dim 1–3 finding exists
- Distinctive: line 64
If recommendation is "Release Not Recommended" → verify at least one Critical Dim 1–3 finding or Nonexistent citation exists
- Very specific: line 94
After self-verification completes (pass or partial pass), the main agent finalizes checkpoint.json:
“Common” is measured: kept by at least 6 in 10 of the 36 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
quality-gate Skill
Self-verification checklist for review outputs (WF1 Step 8).
Primary script: scripts/run-quality-gate.py
Usage: python3 run-quality-gate.py <working_dir> <deliverables_dir> <output_path>
8-Item Self-Verification Checklist
Run each check against the generated outputs. All must pass for clean delivery.
Check 1 — Redline Completeness
Verify: Redline DOCX contains tracked changes for ALL Critical and Major findings in issue-registry.json.
- Count tracked changes in redline → count must match Critical + Major findings that have textual corrections
- Missing tracked change for a Critical finding = self-check failure
- If a particular issue has no explicit textual correction, verify it is still represented by a comment in the redline DOCX
- Each comment must have the correct severity prefix per comment-format-guide.md
Check 2 — Review Comment Integrity
Verify: No review comment in the redline DOCX itself contains a hallucination or unsupported assertion.
- Read each comment → verify it is factually supportable from the document content or verification-audit.json
- A comment saying "이 판례는 존재하지 않습니다" must be backed by
Nonexistentstatus in audit trail - A comment making a legal claim must be traceable to the document's own content
Check 3 — Cover Memo Accuracy
Verify: Cover Memo accurately reflects the issue-registry.json.
- Release recommendation in memo matches review-scorecard.json
- Critical findings listed in memo match issue-registry Critical entries
- No finding in the memo that doesn't exist in issue-registry
- No Critical/Major finding in issue-registry that's missing from the memo
Check 4 — Scorecard Consistency
Verify: Review scorecard scores are consistent with actual findings.
- Dimension with 0 findings should score 9–10
- Dimension with Critical finding should score 1–4
- Overall grade computation matches the average
- No mathematical errors in scoring
- Release recommendation is exactly one of: "Pass", "Pass with Warnings", "Manual Review Required", "Release Not Recommended"
- Grade is exactly one of: A, B, C, D (no plus/minus modifiers)
- Skipped dimensions have
score: null, skipped: trueand are excluded from the average
Check 5 — Audit Trail Completeness
Verify: Verification audit trail is complete per review depth setting.
- Quick Scan: all format-validation-escalated citations verified
- Standard: all dispositive-conclusion citations verified
- Deep Review: all citations verified
- No citation in citation-list.json that's missing from verification-audit.json (at applicable depth)
Check 6 — Clean DOCX Correctness
Verify: Clean DOCX incorporates ONLY Critical/Major textual corrections.
- No Suggestion-level changes accepted in clean version
- No tracked changes remaining in clean DOCX
- Original formatting preserved for non-corrected sections
Check 6A — Redline Mapping Report
Verify: working/redline-mapping-report.json accounts for every issue.
- Critical/Major issues must not be
unmapped - Deep Review target: Critical/Major exact mapping rate ≥90%
- Missing report is a warning for backward compatibility, not a hard fail
Check 7 — Release Recommendation Consistency
Verify: Release recommendation follows the Release Recommendation Rules exactly.
- If recommendation is "Pass" or "Pass with Warnings" → verify no Critical Dim 1–3 finding exists
- If recommendation is "Release Not Recommended" → verify at least one Critical Dim 1–3 finding or Nonexistent citation exists
- Cross-check against review-scorecard.json
Remediation Protocol
| Round | Action |
| Round 1 | Fix all failing items. Re-run checks. |
| Round 2 | Patch only remaining failures. Re-run checks. |
| After Round 2 | Deliver with [Self-Check Warning] flags on unresolved items. Explicitly tell user which checks could not be passed. |
Delivery Format
On pass:
✅ Self-verification complete. All 7 checks passed.
Deliverables saved to: $SECOND_REVIEW_PRIVATE_DIR/output/{matter_id}/round_{N}/deliverables/On partial pass:
⚠️ Self-verification complete with warnings.
Passed: 5/8 checks
Failed: Check 2 (comment integrity), Check 6 (clean DOCX)
[Self-Check Warning] details attached.
Deliverables saved to: $SECOND_REVIEW_PRIVATE_DIR/output/{matter_id}/round_{N}/deliverables/Checkpoint
After self-verification completes (pass or partial pass), the main agent finalizes checkpoint.json:
step_8.status→"completed"step_8.output→"deliverables/quality-gate-report.json"last_completed_step→8- This marks the pipeline as fully complete.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

