Skip to content
Development
Command

/COMMAND_COMPLIANCE_REPORT

Reviewed all command files in `.claude/commands/analysis/` directory to ensure proper usage of: - `mcp__claude-flow__*` tools (preferred) - `npx claude-flow` commands (as fallback) - No direct implementation calls

From plugin
claude-flow
67k194 skills157 agents194 commands1 MCP
Install
> /plugin marketplace add ruvnet/claude-flow

How 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/COMMAND_COMPLIANCE_REPORT

Context preview

What this command does when you run it.

Reviewed all command files in `.claude/commands/analysis/` directory to ensure proper usage of: - `mcp__claude-flow__*` tools (preferred) - `npx claude-flow` commands (as fallback) - No direct implementation calls

Command definition

COMMAND_COMPLIANCE_REPORT.md

Analysis Commands Compliance Report

Overview

Reviewed all command files in `.claude/commands/analysis/` directory to ensure proper usage of:

  • `mcp__claude-flow__*` tools (preferred)
  • `npx claude-flow` commands (as fallback)
  • No direct implementation calls

Files Reviewed

1. token-efficiency.md

**Status**: ✅ Updated **Changes Made**:

  • Replaced `npx ruv-swarm hook session-end --export-metrics` with proper MCP tool call
  • Updated to: `Tool: mcp__claude-flow__token_usage` with appropriate parameters
  • Maintained result format and context

**Before**:

npx ruv-swarm hook session-end --export-metrics

**After**:

Tool: mcp__claude-flow__token_usage
Parameters: {"operation": "session", "timeframe": "24h"}

2. performance-bottlenecks.md

**Status**: ✅ Compliant (No changes needed) **Reason**: Already uses proper `mcp__claude-flow__task_results` tool format

Summary

  • **Total files reviewed**: 2
  • **Files updated**: 1
  • **Files already compliant**: 1
  • **Compliance rate after updates**: 100%

Compliance Patterns Enforced

1. **MCP Tool Usage**: All direct tool calls now use `mcp__claude-flow__*` format 2. **Parameter Format**: JSON parameters properly structured 3. **Command Context**: Preserved original functionality and expected results 4. **Documentation**: Maintained clarity and examples

Recommendations

1. All analysis commands now follow the proper pattern 2. No direct bash commands or implementation calls remain 3. Token usage analysis properly integrated with MCP tools 4. Performance analysis already using correct tool format

The analysis directory is now fully compliant with the Claude Flow command standards.

Read more
Ships withclaude-flow

An agent meta-harness for Claude Code and Codex. Agent = Model + Harness. The model writes; the harness gives it tools, memory, loops, sandboxes, and controls so it can actually work.

Get the whole plugin