Copy one prompt into Cursor, Copilot, Kilo, or any agent with web access.
Install the Neexo skill "test-gate" (test-gate) in this repository.
Manifest: https://awesome.neexo.dk/api/install-manifest?ids=skills%2Ftest-gate
Catalog: https://awesome.neexo.dk/skills/test-gate
Steps:
1. Fetch https://awesome.neexo.dk/api/install-manifest?ids=skills%2Ftest-gate and read the file list.
2. Fetch https://awesome.neexo.dk/api/skills/test-gate/bundle and write every file to the correct project skill folder.
3. Detect IDE from this repo (.cursor → Cursor, .kilo → Kilo).
4. Preserve subdirectory structure (references/, agents/, scripts/, assets/).
5. Confirm which files you wrote.
Copilot — full plugincopilot plugin install neexo-developer@awesome-neexo
Bundle API (JSON)https://awesome.neexo.dk/api/skills/test-gate/bundle
Overview
Before committing or pushing product changes, run the project's documented quality gate. Do not invent a weaker substitute when a unified script exists.
Discover the gate
Prefer pnpm ci:check or npm run ci:check when present
Else use the command named in AGENTS.md / README / playbook notes
Fallback only when no unified gate exists: lint + typecheck/test + build as documented
Workflow
Confirm which package manager and script the repo uses
Run the gate from the repo root (or the documented package in a monorepo)
If the repo has changelog:check (or equivalent) and you touched user-visible product surfaces, ensure changelog check is included — either inside ci:check or run it explicitly
Fix failures; re-run until green
Only then commit / push
Fail closed
Do not commit with failing typecheck, lint, tests, or changelog check
Do not skip the gate with --no-verify unless the user explicitly requests it
Prefer ci:check:quick only while iterating if the repo documents it; run the full gate before push
Relation to other skills
Use product-changelog when fragments are required
Use git-commit after the gate is green
Raw content
Copy into your project — e.g. .instructions.md, .agent.md, or SKILL.md
## Overview
Before committing or pushing product changes, run the project's **documented** quality gate. Do not invent a weaker substitute when a unified script exists.
## Discover the gate
1. Prefer `pnpm ci:check` or `npm run ci:check` when present
2. Else use the command named in AGENTS.md / README / playbook notes
3. Fallback only when no unified gate exists: lint + typecheck/test + build as documented
## Workflow
1. Confirm which package manager and script the repo uses
2. Run the gate from the repo root (or the documented package in a monorepo)
3. If the repo has `changelog:check` (or equivalent) and you touched user-visible product surfaces, ensure changelog check is included — either inside `ci:check` or run it explicitly
4. Fix failures; re-run until green
5. Only then commit / push
## Fail closed
- Do not commit with failing typecheck, lint, tests, or changelog check
- Do not skip the gate with `--no-verify` unless the user explicitly requests it
- Prefer `ci:check:quick` only while iterating if the repo documents it; run the full gate before push
## Relation to other skills
- Use `product-changelog` when fragments are required
- Use `git-commit` after the gate is green