quality-gate
Skill3 starsChanged 21 days agoMITView on GitHub
Run the Greenhouse quality gate before handing off or committing: typecheck, lint (with the plugin boundary check) and the full test suite, then the extra gates the change surface needs (HTTP security e2e, plugin assembly and core-only run, universal client checks and browser suite, desktop), a compliance scan of the changed files, a docs-sync check and a status table. Use for: run the gate / check code quality / pre-commit self check / quality gate, 跑一下门禁, 检查代码质量, 提交前自检, 质量检查. Red lines: never trim the default suite, report red as red.
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 repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-agent-profileSkill
- add-agent-toolSkill
- add-api-routeSkill
- add-client-screenSkill
- add-db-tableSkill
- full-featureSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 36 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 57
No speculative abstractions, unused columns or "for later" hooks.
“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
Source of truth: root AGENTS.md (Verification), the nearest module AGENTS.md, and .github/workflows/ci.yml (what CI runs). This skill is the run order.
Step 1: the core three (every change)
pnpm typecheck # plugins:sync + tsc over the workspace (skips apps/client)
pnpm lint # check-plugin-boundaries + eslint + prettier on apps/ packages/ plugins/
TEST_DATABASE_URL=<loopback db named *test*> pnpm test # unit + db + db-commit- lint failures:
pnpm lint:fix, then rerunpnpm lint. - Iterate with
pnpm test:unit(no PostgreSQL) orpnpm test:db; run fullpnpm testbefore handoff and never trim it. - TEST_DATABASE_URL must be a loopback database with test or e2e in its name (one per worktree, e.g. greenhouse_test_
<slug>); tune with VITEST_UNIT_MAX_WORKERS / VITEST_DB_MAX_WORKERS.
Step 2: gates by change surface
- Auth, permissions, isolation, proxy or MCP:
DATABASE_URL=<migrated loopback e2e db> pnpm test:e2e:ci(tests/e2e, real HTTP, dead LLM endpoint). - plugins/
<id>, apps/api/src/plugin-host or the kit:pnpm plugins:sync --checkandTEST_DATABASE_URL=<…> pnpm test:core(zero packages compiled, real boot); run them one after another, never beside other assembly or build commands. - Kit export list changed: update apps/api/src/tests/extension-kit.snapshot.test.ts and add an
extension-kit:CHANGELOG line. - Fork overlay:
node scripts/check-extension-overlay.mjs --base upstream/main --strict(paths stay in the seam, plugin imports stay public). - Core schema:
./node_modules/.bin/drizzle-kit check; schema-equivalence runs insidepnpm test. - apps/client:
(cd apps/client && pnpm typecheck && pnpm lint),pnpm test:unit apps/client(includes src/theme/design-guard.test.ts),pnpm test:e2e:client, andpnpm app:buildwhen the web export changes. - Parallel worktrees running the client suite set CLIENT_E2E_API_PORT, CLIENT_E2E_WEB_PORT, CLIENT_E2E_DATABASE.
- apps/desktop:
pnpm desktop:check. - Shared tokens (packages/ui/src/tokens):
pnpm tokens:build; never hand-edit generated tokens. - Restricted runners that cannot launch Chromium only collect browser specs; say so in the report.
Step 3: compliance scan (changed files only)
# server logs: no console.* outside CLI output
grep -rn "console\.\(log\|warn\|error\)" apps/api/src plugins --include="*.ts" | grep -v "\.test\." | grep -v "/cli[/.]"
# client isolation and banned APIs
grep -rn "from '@greenhouse/\|@react-navigation/\|KeyboardAvoidingView\|window\.confirm(\|window\.alert(" apps/client/app apps/client/src
# cross-package relative imports (tests and parity checks are exempt)
grep -rn "from '\(\.\./\)\{3,\}\(packages\|apps\|plugins\)/" apps packages plugins --include="*.ts" --include="*.tsx" | grep -v node_modules | grep -v "\.test\."- CLI output (cli/, cli.ts, plugin command handlers) and text inside tool descriptions may mention console; everything else logs with logger.
- Server by hand: data through getDb() services or plugin service bags; chained routes without
: Hono; noanyin responses; model-bound input through sanitizeForPrompt(); error text names the next step and quotes values. - Plugins by hand: imports only from @greenhouse/api/extension-kit, @greenhouse/types/, @greenhouse/crud, @greenhouse/ui, own files and declared dependencies; core never names a plugin id.
- Client by hand: surface per DESIGN.md (sheet/inspector, fixed DIALOG_SIZES); kit components; identity-bound writes; en and zh both updated; no React import in unit-tested modules.
- Intra-package Node ESM imports end in
.js.
Step 4: reuse and anti-entropy
- Server helpers come from @greenhouse/utils/* (date nowIso, json safeJsonParse/extractJson, concurrency runWithConcurrency, logger, crypto, error toErrorMessage/isUniqueViolation, id, semver, html escapeHtml, prompts); the client has its own in src/lib and src/data.
- Deletions cascade: orphaned components, helpers, types, copy keys, routes, nav entries, tests and docs go too.
- A second implementation of the same job is registered with its reason in the relevant AGENTS.md.
- No speculative abstractions, unused columns or "for later" hooks; hooks need a real consumer, Example coverage and seam tests.
- Declared capabilities work; unconfigured paths fail explicitly.
Step 5: docs sync
- Core schema → packages/db/src/db-schema.md (+ packages/db/src/AGENTS.md for rules); plugin tables → plugins/
<id>/db-schema.md. - Profiles → apps/api/src/profiles/agent-profiles.md and profiles/AGENTS.md.
- Server conventions → apps/api/src/AGENTS.md.
- Client conventions → apps/client/AGENTS.md; design rules → apps/client/DESIGN.md.
- Plugin contract → EXTENDING.md + plugins/example + plugins/example/api/tests/seam.test.ts.
- A plugin's behavior → plugins/
<id>/README.md and AGENTS.md. - Desktop → apps/desktop/AGENTS.md; structure and cross-cutting rules → root AGENTS.md; behavior people see → README.md.
Step 6: report
| Check | Status | Notes |
|---|---|---|
| typecheck | ✅/❌ | |
| lint (incl. plugin boundaries) | ✅/❌ | |
| test (unit/db/db-commit) | ✅/❌ | N passed, M failed |
| test:e2e:ci | ✅/❌/— | |
| plugins:sync --check / test:core | ✅/❌/— | |
| client typecheck + lint (apps/client) | ✅/❌/— | |
| test:e2e:client | ✅/❌/— | collected only? |
| desktop:check | ✅/❌/— | |
| compliance scan | ✅/❌ | |
| reuse / anti-entropy | ✅/❌ | |
| docs sync | ✅/❌ | |- Report failures as failures; never skip or weaken a check to make the table green.
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.

