Agent Skills
› NeverSight/learn-skills.dev
› quality-gates
quality-gates
GitHub提供合并前质量门禁指南，涵盖架构门运行、文档审计更新及测试规范。确保依赖合规、通过构建与单元测试，并同步更新审计记录以保障代码质量。
Trigger Scenarios
进行结构变更（如新增依赖或模块）后
修改能力、事件或关键工作流时
提交PR前的检查阶段
涉及测试、指令或QA任务添加时
Install
npx skills add NeverSight/learn-skills.dev --skill quality-gates -g -y
SKILL.md
Frontmatter
{
"name": "quality-gates",
"description": "Auditing, testing, and architecture-governance instructions for Black-Tortoise, covering when to run `architecture:gate`, update docs\/AUDIT-*, ship tests, and satisfy `.github\/instructions\/64-quality-testing-copilot-instructions.md` before merge."
}
Quality Gates & Audit Master Guide
Intent
Document the pre-merge checklist: what gates must pass, which audit artefacts to update, and which tests the repo expects, per .github/instructions/64-quality-testing-copilot-instructions.md.
Gates to Run
- Run
pnpm run architecture:gateafter any structural change (new dependencies, cross-layer imports, new modules); this enforces the dependency cruiser rules described in.github/instructions/61-architectural-governance-copilot-instructions.md. - Before PR, execute
pnpm run lint,pnpm run build -- --noEmit, and the relevant unit suites described in the capability instructions. - Ensure Husky/lint-staged hooks triggered by
git commitpass (eslintandtsc --noEmitperpackage.json).
Documentation & Audit Tracking
- Update
docs/AUDIT-<module>.mdwhenever you change a capability, event, or critical workflow; note invariants, boundaries, and audit findings as specified in.github/instructions/64-quality-testing-copilot-instructions.md. - Document requirements/status in
requirements.mdandtasks.md(status values: not-started, in-progress, completed, blocked) before completion. - Capture
architecture:gatefailures’ logs and include them in your notes so reviewers can see what changed since the last passing gate.
Testing Expectations
- Cover every critical path and domain invariant touched by your change with tests (Jasmine + Karma for unit stores/domains, Playwright for happy-path flows).
- Use Playwright with resilient selectors (
data-testid, roles) and emulator resets so tests are deterministic (.github/skills/e2e-playwrightalready describes these patterns). - When introducing async or signal transitions, do full Arrange-Act-Assert cycles and clean up subscriptions with
takeUntilDestroyed()orrxMethoddisposal.
When to Apply This Skill
- Anytime you add/modify tests, instructions, or GA/QA tasks that must mention gating commands, auditors, or docs.
- Whenever you touch documentation or pipeline scripts so that audit assets remain in sync with the
docs/AUDIT-*expectations.
Version History
- e0220ca Current 2026-07-05 21:27
