← スキル一覧に戻る

quality-gate-validation
by frostaura
A toolkit for building full-stack systems. Battle-tested with Copilot in VS Code, with agents for Github Copilot CLI.
⭐ 23🍴 25📅 2026年1月13日
SKILL.md
name: quality-gate-validation description: Guide for running and validating quality gates (build, lint, test, coverage, regression). Use when validating code, running tests, or checking if a phase can proceed.
Quality Gate Validation
Gate Commands
| Gate | .NET | Node.js |
|---|---|---|
| Build | dotnet build | npm run build |
| Lint | dotnet format --verify-no-changes | npm run lint |
| Test | dotnet test | npm test / npx playwright test |
| Coverage | dotnet test --collect:"XPlat Code Coverage" | npm test -- --coverage |
Coverage Requirement
100% code coverage required for both frontend and backend. No exceptions.
Validation Rule
All gates are binary pass/fail - exit code 0 = pass, anything else = fail.
Retry Strategy
Attempt 1: Fix the identified issue → re-run gate
Attempt 2: Simplify the approach → re-run gate
Attempt 3: Suggest architectural refactor to retain functionality but simplify testability of the code -> get user approval -> implement the changes → re-run gate
Attempt 4: Reduce scope (remove problematic feature) → re-run gate
Still failing: Mark task as "blocked", store reason, continue with other tasks
Phase 7 Validation Checklist
After each feature, ALL must pass:
- Test Suite: Unit + Integration + E2E pass (exit 0)
- Coverage: 100% code coverage (frontend + backend)
- Functional Regression: Manually test features with Playwright (not spec files)
- Visual Regression: Playwright screenshots match baseline
- Performance: Response times within 5% of baseline
- User Journeys: All existing workflows functional
Functional Regression (Manual Testing)
Use Playwright interactively to verify features work - this is NOT writing spec files:
- Navigate to each affected page/component
- Test all user interactions (clicks, forms, navigation)
- Verify data displays correctly
- Check error states and edge cases
- Confirm no console errors
If Validation Fails
- STOP development immediately
- Root cause analysis
- Fix or redesign approach
- Re-validate until 100% pass
- Store:
remember("regression", "feature_x_issue", "[details]")
Store Gate Results
# On success
mcp__gaia__remember("gate", "phase_X", "passed", "ProjectWide")
# On blocked (after 3 attempts)
mcp__gaia__remember("gate", "phase_X_blocked", "[reason and what was tried]", "ProjectWide")
Gate Summary
| Gate | Validates | Failure Action |
|---|---|---|
| Build | Compilation | Fix syntax/type errors |
| Lint | Code style | Run auto-fix or manual fix |
| Test | Functionality | Debug failing tests |
| Coverage | 100% coverage | Add missing tests |
| Functional | Features work | Fix broken functionality |
| Regression | No breakage | Investigate root cause |
スコア
総合スコア
75/100
リポジトリの品質指標に基づく評価
✓SKILL.md
SKILL.mdファイルが含まれている
+20
✓LICENSE
ライセンスが設定されている
+10
✓説明文
100文字以上の説明がある
+10
○人気
GitHub Stars 100以上
0/15
○最近の活動
3ヶ月以内に更新がある
0/10
✓フォーク
10回以上フォークされている
+5
✓Issue管理
オープンIssueが50未満
+5
✓言語
プログラミング言語が設定されている
+5
○タグ
1つ以上のタグが設定されている
0/5
レビュー
💬
レビュー機能は近日公開予定です