Quality Gate

1. Initialization / recompile

/init

• languages / frameworks / SDKs / versions
• package/workspace structure
• app type: web / API / CLI / desktop / mobile / library / IaC
• architecture boundaries
• persistence / queue / cache / external services
• auth / network / filesystem boundaries
• existing test/lint/type/build scripts
• generated-code boundary
• browser / OS / CPU architecture targets
• release/deploy target
• GitHub PR topology: independent / stacked / release trunk

1. framework/runtime/SDK official quality/testing guidance
2. official examples/templates/starters
3. official first-party Actions / CI examples
4. official language/toolchain guidance
5. coherent existing project configuration
6. established maintained ecosystem tooling
7. custom tooling

2. Verification taxonomy

Unit test

• pure/domain logic
• parser / validator / scheduler / algorithm
• state transition
• isolated component behavior
• error handling branch

• logic regressionを局所的・高速に検出
• failure locationを狭くする

Smoke / connectivity test（疎通テスト）

• process/service startup
• health/readiness endpoint
• application -> DB connection
• application -> cache/queue connection
• frontend -> API basic request
• required migration/schema availability
• desktop/mobile app launch
• packaged artifact startup

Integration test（結合テスト）

• API + service + database
• repository + real/test DB
• queue producer + consumer
• auth middleware + endpoint
• filesystem/network adapter + domain
• frontend data layer + API contract
• migration + application read/write

Contract / schema test

• OpenAPI / GraphQL / protobuf
• DB schema compatibility
• event/message schema
• generated client/server compatibility
• public SDK/API contract

E2E / system test

• sign-in -> operation -> persistence -> rendered result
• purchase/scheduling/upload等のcritical journey
• browser/native interaction
• cross-service workflow
• release-like environment smoke + critical scenarios

Manual / visual verification

Verification Executor / native environment

candidate_identity
environment_identity
procedure_or_command
observed_result
evidence_artifacts
source_mutation_observed

3. 動作確認ゲートを変更riskから決める

• 変更したlogic
• 変更したboundary
• runtime/configuration変更
• persistence/schema変更
• user-visible flow変更
• deployment/package変更
• security-sensitive path変更
• failure時のimpact

security-audit

4. Quality profileをproject-localにcompileする

quality/profile.yaml

quality/profile.json

• schema_version

• profile version / updated-at or source revision
• detected framework/runtime/SDK versions
• official guidance source referencesと確認時点
• test taxonomyとproject内の具体例
• change-type -> required verification mapping
• fast worker gate
• ticket integration gate
• stack reconciliation/revalidation policy
• release gate
• canonical validation entry points
• configured CI checks when present
• coverage policy when meaningful
• browser/device/OS/architecture matrix
• native/device/GUI verificationのcandidate materializationとenvironment ownership policy
• CI trigger semantics (

  pull_request

  /

  push

  / schedule / dispatch / comment/review event)
• runner policyとplatform matrixの起動条件
• expensive/native/platform-specific gateの適用条件
• concurrency / cancellation / timeout policy
• artifact/report pathsとretention policy
• repository visibility / included usage / billing modelを踏まえたCI resource policy
• expected CI usage/cost modelまたはbudget guardrail（意味があるprojectのみ）
• failure policy

validate:fast
validate:integration
validate:release

4.1 Semantic validation evidence verification

success

• check context / job名がcandidate SHA上に実在する
• checkが検証対象のcurrent SHA / current PR headを対象としている
• known failureを無視していない
• skipped / neutral / cancelled / unrelated bot successをapplicable validationの代替にしない
• 同名checkでも別workflow / 別event semanticsなら誤同定しない
• Draftのためreviewをskipしたbot status等をrelease validation成功として数えない
• current SHAへ更新後、staleな以前のgreenを再利用しない

main

base == main

head == current release-*

5. 調査だけで終わらず実装する

• formatter / linter / static-analysis config
• compiler / type-check config
• unit/component test infrastructure
• smoke/connectivity test infrastructure
• integration/contract/E2E infrastructure
• framework/platform-specific validation
• documentation tests
• dependency/static analysis
• coverage configuration
• schema/migration validation
• browser/device/OS/architecture matrices
• production build/package checks
• code/dependency/security checks
• project-local specialized Agent Skills

• .github/workflows/*

• required CI check structure

6. Framework-native checksを優先する

7. Agent Skills / toolingもstack-awareにする

1. existing deterministic project command
2. framework/runtime official CLI
3. short project-local Skill wrapping deterministic tools
4. native agent capability
5. 明確な優位があるplugin/MCP

7.1 Delivery-estimation integration

agent-delivery-estimation

• validation level / required gate
• CI started/completed duration
• queue / retry / failure
• E2E / manual verification wait
• release-only validation cost
• current-SHA revalidationによる追加round

8. GitHub Actions / CI resource efficiency

8.1 実測してから最適化する

• repository visibility
• workflow / event / branch
• job count
• runner label / OS / architecture
• job started/completed timeまたはbillable duration
• success / failure / cancelled / skipped
• 同一commit/SHAに対する重複run
• artifact / cache usage when relevant
• billing/usage画面または利用可能なusage API

expected CI usage ≈ trigger frequency × started jobs × billed duration × runner cost/weight

workflow runs = N

8.2 trigger duplicationを避ける

push

pull_request

• ticket/feature branch:

  pull_request

  でintegration gate

• main

  / release trunk / tag:

  push

  でpost-mergeまたはrelease-specific gate
• manual deep verification:

  workflow_dispatch

• periodic verificationに実際の意味がある場合のみ

  schedule

push.branches: ['**']

pull_request

8.3 fast PR gateとexpensive platform gateを分離する

• platform/native関連pathが変更された
• platform-specific behavior / packaging / process invocationが変更された
• release candidate / release trunk / tag
• explicit label / manual dispatchによるfull verification
• required compatibility matrixを定期的に再確認する必要がある

8.4 expensive jobはrunner allocation前にgateする

• workflow

  paths

  /

  paths-ignore

• event / branch filter
• job-level

  if

• lightweight preflight jobからのoutputを使ったdependent expensive jobの条件分岐

8.5 comment/review-driven automationを事前filterする

issue_comment

pull_request_review_comment

pull_request_review

• explicit trigger phrase / command
• intended event type
• trusted actor / permission条件 when necessary
• bot-generated noiseの除外

8.6 superseded CIをcancelする

concurrency

cancel-in-progress: true

8.7 timeoutを明示する

timeout-minutes

8.8 artifact / cacheは目的別に管理する

• CI evidence / debug artifact: 必要な期間だけ短く保持
• release deliverable: release policyに従う
• artifactが不要ならuploadしない
• cacheは実測でbuild/test時間を改善する場合に使う

8.9 CIを削るのではなく境界を再配置する

• quota不足を理由にrequired verificationを無断削除する
• native/platform testを単に消してgreenにする
• required verificationをdisableしてusage問題を隠す
• self-hosted runnerへ移せば安全性検討不要とみなす

8.10 budgetはlast guardrailにする

1. included usageとactual monthly burnを確認
2. trigger duplication / unnecessary platform jobs / runaway jobsを先に修正
3. optimized baselineを1 billing cycle観測 4.通常利用 + 合理的headroomにbudgetを設定
4. usage spike時は「回数」ではなくrunner/job単位で再計測

8.11 反復テストの適応的な頻度制御

9. Worker gate

10. Ticket integration gate

• independent ticket:

  <issue-number> -> release-x-y-z

• stacked dependent ticket:

  <issue-number> -> <immediate-predecessor-ticket-branch>

• acceptance criteriaに対応するverification
• changed boundaryに必要なunit/smoke/integration/contract/E2E
• formatter/lint/type/static/build等のapplicable checks
• required CI checks
• current head SHAまたはcurrent head SHA / snapshotにprovenanceで結び付いたimmutable artifact identityとvalidation evidenceの一致
• immediate PR base / target release trunkとのstaleness確認

11. Stack reconciliation gate

• previous

  validated_sha

  とcurrent head SHAを比較
• SHAが変わったdownstream ticketではaffected required verificationを再実行
• old green resultをcurrent headのpassとして流用しない
• configured CI/checksが存在する場合はcurrent headで再評価
• predecessor contract/API/schema変更時はdependent contract/integration testを優先して再評価

12. Release gate

release-x-y-z -> main

• full integration suite
• clean production build/package
• release artifact smoke test
• critical user-journey E2E
• supported browser/device/OS matrix
• migration rehearsal
• packaging/signing/notarization
• deployment/IaC validation
• upgrade/backward-compatibility
• release-like environment smoke

13. PR readiness gate

• Issue acceptance criteriaを満たす
• required verification levelを満たす
• configured CI/checksが存在する場合はcurrent SHAで失敗を残していない
• blocking review解消
• known limitationを隠さない
• target release trunk / immediate predecessorとのstaleness確認
• stack update後のaffected revalidation完了
• PR metadata / linked Issueがcurrent delivery stateと一致

github-delivery

14. False green禁止

• skipped test /

  .only

• blanket ignore/suppression
• ignored exit code /

  || true

• no-fail option
• CI check disabling
• broad generated-code excuse
• mock-only testをreal integrationと報告
• manual check未実施を「動作確認済み」と報告
• coverage threshold低下や不当exclude
• predecessor変更後にold SHAのgreen resultを流用

15. Coverageは固定万能指標にしない

16. Re-evaluation triggers

• framework/runtime upgrade
• official testing guidance変更
• architecture boundary変更
• new app/platform target
• CI workflow変更
• PR/stack/release integration model変更
• flaky/slow gateが開発速度を阻害
• Actions usage/costが想定baselineから大きく乖離
• included usage / runner billing model / repository visibility変更
• escaped regressionがgateの穴を示した
• release process変更