quality-gate
Skill7 starsChanged 9 months agoMITView on GitHub
Run full validation suite (make check + gopls diagnostics) and report structured pass/fail. Usage: /quality-gate [package...]
45 other projects use a version of this.
Adopted by
Most recently taken up by
- Fili999/ai-hubtheir own version, first seen Nov 15, 2026
- shimo4228/writingtheir own version, first seen Nov 15, 2026
- jodyjdc/ultimate-best-seller-studiotheir own version, first seen Nov 8, 2026
- unlockers-ai/unlockers-skills-librarytheir own version, first seen Nov 8, 2026
- TerryFYL/ai-research-armytheir own version, first seen Nov 8, 2026
- Romandredan/1c-quality-gatetheir own version, first seen Nov 4, 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 versions45 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 45
- RapierCraftStudios/ForgeDock★ 119same name
- microsoft/webui★ 102same name
- impecablemee/gtm-mcp★ 66same name
- microsoft/devsquad-copilot★ 50same name
- Romandredan/1c-quality-gate★ 49same name
- TerryFYL/ai-research-army★ 9same name
- Felpix-Studios/social-science-research★ 8same name
- BerryKuipers/claude-code-toolkit★ 7same name
- freskhu/genesis★ 5same name
- unlockers-ai/unlockers-skills-library★ 4same name
35 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 repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- plugin/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- corpus-testSkill
- gen-testSkill
- prepare-releaseSkill
- prereviewSkill
- publish-releaseSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 36 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Run the complete quality pipeline and report structured results.
- Distinctive: line 19
If packages were specified as arguments, use those.
- Very specific: line 41
Use the go_diagnostics MCP tool on changed .go files (NOT bash).
- Distinctive: line 73
If there are fixable issues, offer:
“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
Run the complete quality pipeline and report structured results.
Usage:
/quality-gate— validate all changed packages/quality-gate parser validator— validate specific packages
Step 1: Identify Scope
Determine which packages to check.
If packages were specified as arguments, use those.
Otherwise, find changed .go files:
git diff --name-only HEADThen extract unique package directories from the output using string processing — do NOT use piped bash commands (they trigger permission prompts). Convert relative paths to absolute paths (prepend the repo root) for Step 3.
Step 2: Run make check
This runs tidy, fmt, lint, and tests in one command:
make checkRecord pass/fail and capture any output.
Step 3: Run gopls Diagnostics
Use the go_diagnostics MCP tool on changed .go files (NOT bash). Pass absolute paths.
Categorize results:
- 🔴 Errors — must fix
- 🟡 Warnings — should fix
- 💡 Hints — fix for performance (5-15% impact documented)
Step 4: Report
Present results in this format:
## Quality Gate Results
### `make check`: ✅ PASS / ❌ FAIL
[details if failed]
### gopls Diagnostics
| File | Level | Message | Suggested Fix (if any) |
|------|-------|---------|------------------------|
| ... | ... | ... | ... |
### Verdict: ✅ READY / ❌ NOT READY
Issues to address:
1. [issue]
2. [issue]Step 5: Offer Actions
If there are fixable issues, offer:
- Fix all — address all findings automatically
- Fix errors only — address blocking issues
- Skip — acknowledge and continue
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.