/f5-status
Status dashboard, health checks, and self-diagnostics
$ 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-status
Context preview
What this command does when you run it.
Status dashboard, health checks, and self-diagnostics
Command definition
f5-status.mddescription: Status dashboard, health checks, and self-diagnostics
argument-hint: [status|doctor|selftest|health] [options]
/f5-status - Unified Status & Diagnostics Command
**Consolidated command** that replaces:
- `/f5-doctor` → `/f5-status doctor`
- `/f5-selftest` → `/f5-status selftest`
ARGUMENTS
$ARGUMENTS
MODE DETECTION
| Pattern | Mode | Description | |---------|------|-------------| | `doctor` | DOCTOR | Framework health check | | `selftest [options]` | SELFTEST | Self-diagnostics suite | | `health` | HEALTH | Health dashboard | | `<other>` (default) | STATUS | Project status dashboard |
---
MODE: DOCTOR (from /f5-doctor)
`/f5-status doctor`
Check F5 Framework health in current project.
**Checks:** 1. F5 Framework installation (.f5/ directory) 2. Config validation (config.json) 3. Version check (local vs global) 4. MCP server connectivity 5. Gate configuration 6. Command availability
**Examples:**
/f5-status doctor
/f5-status doctor --verbose
/f5-status doctor --fix
---
MODE: SELFTEST (from /f5-selftest)
`/f5-status selftest [options]`
Run diagnostic tests to verify F5 Framework installation.
| Option | Description | |--------|-------------| | `--full` | Run all tests | | `--suite <name>` | Specific test suite (quick/standard/full/mcp) | | `--fix` | Auto-fix issues | | `--category <name>` | Specific category (config/memory/gates/mcp/commands) |
**Examples:**
/f5-status selftest
/f5-status selftest --full
/f5-status selftest --suite mcp
/f5-status selftest --fix
---
MODE: STATUS (Default)
Display comprehensive project status with per-requirement tracking.
STEP 0: RESOLVE LANGUAGE
Resolve active language for output labels.
resolve_language() {
# 1. Check --lang flag
if [ -n "$LANG_FLAG" ]; then echo "$LANG_FLAG"; return; fi
# 2. Check project config
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
# 3. Check global preference
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
# 4. Default
echo "en"
}
ACTIVE_LANG=$(resolve_language)i18n Labels Reference
| Key | en | vi | ja | |-----|----|----|-----| | title | Project Status Dashboard | Bảng điều khiển dự án | プロジェクトステータスダッシュボード | | overall_progress | Overall Progress | Tiến độ tổng thể | 全体進捗 | | gate_matrix | Gate Completion Matrix | Ma trận hoàn thành Gate | ゲート完了マトリックス | | by_developer | Progress by Developer | Tiến độ theo Developer | 開発者別進捗 | | by_gate | Requirements by Gate | Yêu cầu theo Gate | ゲート別要件 | | blocked_reqs | Blocked Requirements | Yêu cầu bị chặn | ブロックされた要件 | | no_blockers | No blocked requirements | Không có yêu cầu bị chặn | ブロックされた要件はありません | | summary | Summary | Tóm tắt | サマリー | | total | Total | Tổng | 合計 | | completed | Completed | Hoàn thành | 完了 | | in_progress | In Progress | Đang tiến hành | 進行中 | | blocked | Blocked | Bị chặn | ブロック中 | | pending | Pending | Đang chờ | 保留中 |
OVERVIEW
Quick status view of entire F5 Framework state with health scoring.
---
HEALTH DASHBOARD
`/f5-status health`
═══════════════════════════════════════════════════════════════
F5 HEALTH DASHBOARD
═══════════════════════════════════════════════════════════════
🏥 OVERALL HEALTH SCORE
───────────────────────────────────────────────────────────────
[████████████████████░░░░] 82/100 ✅ Good
📊 CATEGORY BREAKDOWN
───────────────────────────────────────────────────────────────
🏥 System [██████████████████░░] 92% ✅
⚙️ Configuration [████████████████░░░░] 85% ✅
🔄 Workflow [██████████████░░░░░░] 72% 🔶
✨ Quality [████████████████░░░░] 80% ✅
🔗 Integration [██████████████░░░░░░] 78% ✅
📋 KEY METRICS
───────────────────────────────────────────────────────────────
✅ Configuration Valid
✅ Memory System Initialized
✅ Commands Available (15)
⚠️ Gate Progress: 1 day behind schedule
✅ Traceability: 92%
✅ Error Rate: 3.2%
⚠️ MCP Fallback Rate: 12%
✅ Test Coverage: 84%
🚨 ACTIVE ISSUES (2)
───────────────────────────────────────────────────────────────
• ⚠️ Gate D4 behind schedule (Priority: 2)
• ⚠️ Serena MCP fallback rate high (Priority: 3)
💡 RECOMMENDATIONS
───────────────────────────────────────────────────────────────
1. Review Gate D4 blockers - consider escalation
2. Check Serena MCP configuration
3. Continue using TDD for new features
═══════════════════════════════════════════════════════════════
Last Updated: 2024-01-15 10:30:00 | Next Check: Auto on /f5-load
═══════════════════════════════════════════════════════════════Health Score Ranges
| Score | Label | Icon | Meaning | |-------|-------|------|---------| | 90-100 | Excellent | 🌟 | All systems optimal | | 75-89 | Good | ✅ | Minor issues only | | 60-74 | Fair | 🔶 | Attention needed | | 40-59 | Poor | ⚠️ | Multiple issues | | 0-39 | Critical | 🔴 | Immediate action required |
Health Categories
| Category | Icon | What it Measures | |----------|------|------------------| | System | 🏥 | Core framework components | | Configuration | ⚙️ | Project settings | | Workflow | 🔄 | Gate progress, blockers | | Quality | ✨ | Error rate, test coverage | | Integration | 🔗 | MCP availability |
---
ACTION: DEFAULT
`/f5-status`
╔══════════════════════════════════════════════════════════════════╗
║ F5 FRAMEWORK STATUS ║
╠══════════════════════════════════════════════════════════════════╣
║ ║
║ ┌─ PROJECT ───────────────────────────────────
Read more
description: Status dashboard, health checks, and self-diagnostics argument-hint: [status|doctor|selftest|health] [options]
/f5-status - Unified Status & Diagnostics Command
**Consolidated command** that replaces:
- `/f5-doctor` → `/f5-status doctor`
- `/f5-selftest` → `/f5-status selftest`
ARGUMENTS
$ARGUMENTS
MODE DETECTION
| Pattern | Mode | Description | |---------|------|-------------| | `doctor` | DOCTOR | Framework health check | | `selftest [options]` | SELFTEST | Self-diagnostics suite | | `health` | HEALTH | Health dashboard | | `<other>` (default) | STATUS | Project status dashboard |
---
MODE: DOCTOR (from /f5-doctor)
`/f5-status doctor`
Check F5 Framework health in current project.
**Checks:** 1. F5 Framework installation (.f5/ directory) 2. Config validation (config.json) 3. Version check (local vs global) 4. MCP server connectivity 5. Gate configuration 6. Command availability
**Examples:**
/f5-status doctor /f5-status doctor --verbose /f5-status doctor --fix
---
MODE: SELFTEST (from /f5-selftest)
`/f5-status selftest [options]`
Run diagnostic tests to verify F5 Framework installation.
| Option | Description | |--------|-------------| | `--full` | Run all tests | | `--suite <name>` | Specific test suite (quick/standard/full/mcp) | | `--fix` | Auto-fix issues | | `--category <name>` | Specific category (config/memory/gates/mcp/commands) |
**Examples:**
/f5-status selftest /f5-status selftest --full /f5-status selftest --suite mcp /f5-status selftest --fix
---
MODE: STATUS (Default)
Display comprehensive project status with per-requirement tracking.
STEP 0: RESOLVE LANGUAGE
Resolve active language for output labels.
resolve_language() {
# 1. Check --lang flag
if [ -n "$LANG_FLAG" ]; then echo "$LANG_FLAG"; return; fi
# 2. Check project config
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
# 3. Check global preference
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
# 4. Default
echo "en"
}
ACTIVE_LANG=$(resolve_language)i18n Labels Reference
| Key | en | vi | ja | |-----|----|----|-----| | title | Project Status Dashboard | Bảng điều khiển dự án | プロジェクトステータスダッシュボード | | overall_progress | Overall Progress | Tiến độ tổng thể | 全体進捗 | | gate_matrix | Gate Completion Matrix | Ma trận hoàn thành Gate | ゲート完了マトリックス | | by_developer | Progress by Developer | Tiến độ theo Developer | 開発者別進捗 | | by_gate | Requirements by Gate | Yêu cầu theo Gate | ゲート別要件 | | blocked_reqs | Blocked Requirements | Yêu cầu bị chặn | ブロックされた要件 | | no_blockers | No blocked requirements | Không có yêu cầu bị chặn | ブロックされた要件はありません | | summary | Summary | Tóm tắt | サマリー | | total | Total | Tổng | 合計 | | completed | Completed | Hoàn thành | 完了 | | in_progress | In Progress | Đang tiến hành | 進行中 | | blocked | Blocked | Bị chặn | ブロック中 | | pending | Pending | Đang chờ | 保留中 |
OVERVIEW
Quick status view of entire F5 Framework state with health scoring.
---
HEALTH DASHBOARD
`/f5-status health`
═══════════════════════════════════════════════════════════════
F5 HEALTH DASHBOARD
═══════════════════════════════════════════════════════════════
🏥 OVERALL HEALTH SCORE
───────────────────────────────────────────────────────────────
[████████████████████░░░░] 82/100 ✅ Good
📊 CATEGORY BREAKDOWN
───────────────────────────────────────────────────────────────
🏥 System [██████████████████░░] 92% ✅
⚙️ Configuration [████████████████░░░░] 85% ✅
🔄 Workflow [██████████████░░░░░░] 72% 🔶
✨ Quality [████████████████░░░░] 80% ✅
🔗 Integration [██████████████░░░░░░] 78% ✅
📋 KEY METRICS
───────────────────────────────────────────────────────────────
✅ Configuration Valid
✅ Memory System Initialized
✅ Commands Available (15)
⚠️ Gate Progress: 1 day behind schedule
✅ Traceability: 92%
✅ Error Rate: 3.2%
⚠️ MCP Fallback Rate: 12%
✅ Test Coverage: 84%
🚨 ACTIVE ISSUES (2)
───────────────────────────────────────────────────────────────
• ⚠️ Gate D4 behind schedule (Priority: 2)
• ⚠️ Serena MCP fallback rate high (Priority: 3)
💡 RECOMMENDATIONS
───────────────────────────────────────────────────────────────
1. Review Gate D4 blockers - consider escalation
2. Check Serena MCP configuration
3. Continue using TDD for new features
═══════════════════════════════════════════════════════════════
Last Updated: 2024-01-15 10:30:00 | Next Check: Auto on /f5-load
═══════════════════════════════════════════════════════════════Health Score Ranges
| Score | Label | Icon | Meaning | |-------|-------|------|---------| | 90-100 | Excellent | 🌟 | All systems optimal | | 75-89 | Good | ✅ | Minor issues only | | 60-74 | Fair | 🔶 | Attention needed | | 40-59 | Poor | ⚠️ | Multiple issues | | 0-39 | Critical | 🔴 | Immediate action required |
Health Categories
| Category | Icon | What it Measures | |----------|------|------------------| | System | 🏥 | Core framework components | | Configuration | ⚙️ | Project settings | | Workflow | 🔄 | Gate progress, blockers | | Quality | ✨ | Error rate, test coverage | | Integration | 🔗 | MCP availability |
---
ACTION: DEFAULT
`/f5-status`
╔══════════════════════════════════════════════════════════════════╗ ║ F5 FRAMEWORK STATUS ║ ╠══════════════════════════════════════════════════════════════════╣ ║ ║ ║ ┌─ PROJECT ───────────────────────────────────
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

