/f5-gate
Quality gate management with evidence collection
$ npx -y skills add Fujigo-Software/f5-framework-claude --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/f5-gate
Context preview
What this command does when you run it.
Quality gate management with evidence collection
Command definition
f5-gate.mddescription: Quality gate management with evidence collection
argument-hint: <check|complete|enforce> <gate>
mcp-servers: sequential-thinking, github
/f5-gate - Quality Gate Management Command
Manage and enforce quality gates (D1-D4, G2-G4) for Japanese outsource workflow with automated validation and evidence collection.
ARGUMENTS
The user's request is: $ARGUMENTS
STEP 0: RESOLVE LANGUAGE
resolve_language() {
if [ -f ".f5/config.json" ]; then
PROJECT_LANG=$(jq -r '.language // empty' .f5/config.json 2>/dev/null)
if [ -n "$PROJECT_LANG" ] && [ "$PROJECT_LANG" != "null" ]; then echo "$PROJECT_LANG"; return; fi
fi
if [ -f ~/.f5/preferences.yaml ]; then
GLOBAL_LANG=$(grep '^language:' ~/.f5/preferences.yaml 2>/dev/null | sed 's/language:[[:space:]]*"\{0,1\}\([^"]*\)"\{0,1\}/\1/')
if [ -n "$GLOBAL_LANG" ]; then echo "$GLOBAL_LANG"; return; fi
fi
echo "en"
}
ACTIVE_LANG=$(resolve_language)i18n Labels
| Key | en | vi | ja | |-----|----|----|-----| | check_title | Gate Check | Kiểm tra Gate | ゲートチェック | | status_title | Gate Status | Trạng thái Gate | ゲートステータス | | prerequisites | Prerequisites | Điều kiện tiên quyết | 前提条件 | | checklist | Checklist Verification | Xác minh danh sách | チェックリスト検証 | | automated_checks | Automated Checks | Kiểm tra tự động | 自動チェック | | evidence | Evidence Collected | Bằng chứng đã thu thập | 収集したエビデンス | | passed | PASSED | ĐẠT | 合格 | | failed | FAILED | KHÔNG ĐẠT | 不合格 | | with_warnings | PASSED WITH WARNINGS | ĐẠT VỚI CẢNH BÁO | 警告付き合格 |
Gate Names by Language
| Gate | en | vi | ja | |------|----|----|-----| | D1 | Research Complete | Nghiên cứu hoàn thành | 調査完了 | | D2 | SRS Approved | SRS được duyệt | SRS承認済 | | D3 | Basic Design Approved | Thiết kế cơ bản được duyệt | 基本設計承認済 | | D4 | Detail Design Approved | Thiết kế chi tiết được duyệt | 詳細設計承認済 | | G2 | Implementation Ready | Triển khai hoàn thành | 実装完了 | | G2.5 | Verification Complete | Xác minh hoàn thành | 検証完了 | | G3 | Testing Complete | Kiểm thử hoàn thành | テスト完了 | | G4 | Deployment Ready | Sẵn sàng triển khai | デプロイ準備完了 |
STEP 1: PARSE ACTION
| Action | Description | |--------|-------------| | `check <gate>` | Run comprehensive automated checks for a gate | | `start <gate>` | Start gate review process | | `complete <gate>` | Mark gate as complete | | `status` | Show all gates status | | `report <gate>` | Generate comprehensive gate report for stakeholders | | `enforce <gate>` | Enforce gate requirements - block progress if not met |
STEP 2: DETECT STACK AND COMMANDS
Before running automated checks, detect stack and use appropriate commands:
Stack Detection
STACK=$(jq -r '.stack.backend[0] // .stack.backend // "unknown"' .f5/config.json)
FRONTEND=$(jq -r '.stack.frontend // "unknown"' .f5/config.json)
Stack-Specific Commands
| Check | NestJS | Spring | Django/FastAPI | Go | React/NextJS | |-------|--------|--------|----------------|-----|--------------| | Lint | `npm run lint` | `./mvnw checkstyle:check` | `flake8 .` | `golangci-lint run` | `npm run lint` | | Type | `npm run build` | `./mvnw compile` | `mypy .` | `go build ./...` | `npm run type-check` | | Test | `npm run test` | `./mvnw test` | `pytest` | `go test ./...` | `npm run test` | | Coverage | `npm run test:cov` | `./mvnw jacoco:report` | `pytest --cov` | `go test -cover` | `npm run test:cov` | | Security | `npm audit` | `./mvnw dependency-check:check` | `safety check` | `gosec ./...` | `npm audit` |
Dynamic Command Resolution
# Load from .f5/config/gates.yaml → stack_commands
commands:
lint: "{{stack_commands[stack].lint}}"
test: "{{stack_commands[stack].test}}"
coverage: "{{stack_commands[stack].test_cov}}"
security: "{{stack_commands[stack].security}}"GATE OVERVIEW
| Gate | Name | Japanese | Phase | Prerequisites | |------|------|----------|-------|---------------| | D1 | Research Complete | 調査完了 | Requirements | - | | D2 | SRS Approved | SRS承認 | Requirements | D1 | | D3 | Basic Design Approved | 基本設計承認 | Design | D2 | | D4 | Detail Design Approved | 詳細設計承認 | Design | D3 | | G2 | Implementation Ready | 実装完了 | Implementation | D4 | | G3 | Testing Complete | テスト完了 | Testing | G2 | | G4 | Deployment Ready | デプロイ準備完了 | Release | G3 |
---
GATE ENFORCEMENT (G2-G4)
G2 - Implementation Ready Enforcement
# G2 Automated Enforcement
g2_enforcement:
# Phase 1: Prerequisites
prerequisites:
- gate: "D4"
status: "passed"
error: "D4 (Detail Design) must be completed first"
# Phase 2: Code Quality (via /f5-review)
code_quality:
lint:
command: "npm run lint || yarn lint || eslint ."
required: true
threshold: 0 # No lint errors allowed
error: "Lint errors must be fixed"
type_check:
command: "npm run typecheck || tsc --noEmit"
required: true
threshold: 0 # No type errors
error: "Type errors must be fixed"
complexity:
tool: "complexity-report"
threshold: 10 # Cyclomatic complexity
error: "High complexity code must be refactored"
duplication:
tool: "jscpd"
threshold: 5 # Max 5% duplication
error: "Duplicated code must be reduced"
# Phase 3: Architecture Compliance
architecture:
clean_architecture:
check: "Verify layer separation"
required: true
traceability:
pattern: "REQ-|FR-|NFR-|UC-|US-|SPEC-"
coverage: 100 # All implementations must have traceability comments
error: "All code must have traceability comments (REQ-XXX)"
# Phase 4: Security (via /f5-review security)
security:
owasp_top10:
required: true
checks:
- injection: "SQL/NoSQL/Command injection"
- broken_auth: "Authentication vulnerabilities"
- sensitive_data: "Data exposure risks"
- xxe: "XML External Entities"
- access_control: "Broken access control"
- misconfig: "Security misconfiguration"
- xss:Read more
description: Quality gate management with evidence collection argument-hint: <check|complete|enforce> <gate> mcp-servers: sequential-thinking, github
/f5-gate - Quality Gate Management Command
Manage and enforce quality gates (D1-D4, G2-G4) for Japanese outsource workflow with automated validation and evidence collection.
ARGUMENTS
The user's request is: $ARGUMENTS
STEP 0: RESOLVE LANGUAGE
resolve_language() {
if [ -f ".f5/config.json" ]; then
PROJECT_LANG=$(jq -r '.language // empty' .f5/config.json 2>/dev/null)
if [ -n "$PROJECT_LANG" ] && [ "$PROJECT_LANG" != "null" ]; then echo "$PROJECT_LANG"; return; fi
fi
if [ -f ~/.f5/preferences.yaml ]; then
GLOBAL_LANG=$(grep '^language:' ~/.f5/preferences.yaml 2>/dev/null | sed 's/language:[[:space:]]*"\{0,1\}\([^"]*\)"\{0,1\}/\1/')
if [ -n "$GLOBAL_LANG" ]; then echo "$GLOBAL_LANG"; return; fi
fi
echo "en"
}
ACTIVE_LANG=$(resolve_language)i18n Labels
| Key | en | vi | ja | |-----|----|----|-----| | check_title | Gate Check | Kiểm tra Gate | ゲートチェック | | status_title | Gate Status | Trạng thái Gate | ゲートステータス | | prerequisites | Prerequisites | Điều kiện tiên quyết | 前提条件 | | checklist | Checklist Verification | Xác minh danh sách | チェックリスト検証 | | automated_checks | Automated Checks | Kiểm tra tự động | 自動チェック | | evidence | Evidence Collected | Bằng chứng đã thu thập | 収集したエビデンス | | passed | PASSED | ĐẠT | 合格 | | failed | FAILED | KHÔNG ĐẠT | 不合格 | | with_warnings | PASSED WITH WARNINGS | ĐẠT VỚI CẢNH BÁO | 警告付き合格 |
Gate Names by Language
| Gate | en | vi | ja | |------|----|----|-----| | D1 | Research Complete | Nghiên cứu hoàn thành | 調査完了 | | D2 | SRS Approved | SRS được duyệt | SRS承認済 | | D3 | Basic Design Approved | Thiết kế cơ bản được duyệt | 基本設計承認済 | | D4 | Detail Design Approved | Thiết kế chi tiết được duyệt | 詳細設計承認済 | | G2 | Implementation Ready | Triển khai hoàn thành | 実装完了 | | G2.5 | Verification Complete | Xác minh hoàn thành | 検証完了 | | G3 | Testing Complete | Kiểm thử hoàn thành | テスト完了 | | G4 | Deployment Ready | Sẵn sàng triển khai | デプロイ準備完了 |
STEP 1: PARSE ACTION
| Action | Description | |--------|-------------| | `check <gate>` | Run comprehensive automated checks for a gate | | `start <gate>` | Start gate review process | | `complete <gate>` | Mark gate as complete | | `status` | Show all gates status | | `report <gate>` | Generate comprehensive gate report for stakeholders | | `enforce <gate>` | Enforce gate requirements - block progress if not met |
STEP 2: DETECT STACK AND COMMANDS
Before running automated checks, detect stack and use appropriate commands:
Stack Detection
STACK=$(jq -r '.stack.backend[0] // .stack.backend // "unknown"' .f5/config.json) FRONTEND=$(jq -r '.stack.frontend // "unknown"' .f5/config.json)
Stack-Specific Commands
| Check | NestJS | Spring | Django/FastAPI | Go | React/NextJS | |-------|--------|--------|----------------|-----|--------------| | Lint | `npm run lint` | `./mvnw checkstyle:check` | `flake8 .` | `golangci-lint run` | `npm run lint` | | Type | `npm run build` | `./mvnw compile` | `mypy .` | `go build ./...` | `npm run type-check` | | Test | `npm run test` | `./mvnw test` | `pytest` | `go test ./...` | `npm run test` | | Coverage | `npm run test:cov` | `./mvnw jacoco:report` | `pytest --cov` | `go test -cover` | `npm run test:cov` | | Security | `npm audit` | `./mvnw dependency-check:check` | `safety check` | `gosec ./...` | `npm audit` |
Dynamic Command Resolution
# Load from .f5/config/gates.yaml → stack_commands
commands:
lint: "{{stack_commands[stack].lint}}"
test: "{{stack_commands[stack].test}}"
coverage: "{{stack_commands[stack].test_cov}}"
security: "{{stack_commands[stack].security}}"GATE OVERVIEW
| Gate | Name | Japanese | Phase | Prerequisites | |------|------|----------|-------|---------------| | D1 | Research Complete | 調査完了 | Requirements | - | | D2 | SRS Approved | SRS承認 | Requirements | D1 | | D3 | Basic Design Approved | 基本設計承認 | Design | D2 | | D4 | Detail Design Approved | 詳細設計承認 | Design | D3 | | G2 | Implementation Ready | 実装完了 | Implementation | D4 | | G3 | Testing Complete | テスト完了 | Testing | G2 | | G4 | Deployment Ready | デプロイ準備完了 | Release | G3 |
---
GATE ENFORCEMENT (G2-G4)
G2 - Implementation Ready Enforcement
# G2 Automated Enforcement
g2_enforcement:
# Phase 1: Prerequisites
prerequisites:
- gate: "D4"
status: "passed"
error: "D4 (Detail Design) must be completed first"
# Phase 2: Code Quality (via /f5-review)
code_quality:
lint:
command: "npm run lint || yarn lint || eslint ."
required: true
threshold: 0 # No lint errors allowed
error: "Lint errors must be fixed"
type_check:
command: "npm run typecheck || tsc --noEmit"
required: true
threshold: 0 # No type errors
error: "Type errors must be fixed"
complexity:
tool: "complexity-report"
threshold: 10 # Cyclomatic complexity
error: "High complexity code must be refactored"
duplication:
tool: "jscpd"
threshold: 5 # Max 5% duplication
error: "Duplicated code must be reduced"
# Phase 3: Architecture Compliance
architecture:
clean_architecture:
check: "Verify layer separation"
required: true
traceability:
pattern: "REQ-|FR-|NFR-|UC-|US-|SPEC-"
coverage: 100 # All implementations must have traceability comments
error: "All code must have traceability comments (REQ-XXX)"
# Phase 4: Security (via /f5-review security)
security:
owasp_top10:
required: true
checks:
- injection: "SQL/NoSQL/Command injection"
- broken_auth: "Authentication vulnerabilities"
- sensitive_data: "Data exposure risks"
- xxe: "XML External Entities"
- access_control: "Broken access control"
- misconfig: "Security misconfiguration"
- xss:AI-Powered Development Framework for Claude Code
Repo: Fujigo-Software/f5-framework-claude
Other commands on f5-framework.
- /f5-agent
Manage AI agents, personas, and get smart suggestions
Open command - /f5-analytics
View project analytics and metrics
Open command - /f5-ba
Business analysis workflow
Open command - /f5-backend
Backend development commands
Open command - /f5-checkpoint
[DEPRECATED] Use /f5-ctx checkpoint
Open command - /f5-classify
Classify input files by type using content-first analysis, detect gaps, and generate coverage declaration
Open command

