Template

Files

lmiranda b5d36865ee feat(plugins): add Visual Output headers to all other plugin commands

Add single-line visual headers to 66 command files across 10 plugins:
- clarity-assist (2 commands): 💬
- claude-config-maintainer (5 commands): ⚙️
- cmdb-assistant (11 commands): 🖥️
- code-sentinel (3 commands): 🔒
- contract-validator (5 commands): ✅
- data-platform (10 commands): 📊
- doc-guardian (5 commands): 📝
- git-flow (8 commands): 🔀
- pr-review (7 commands): 🔍
- viz-platform (10 commands): 🎨

Each command now displays a consistent header at execution start:
┌────────────────────────────────────────────────────────────────┐
│  [icon] PLUGIN-NAME · Command Description                       │
└────────────────────────────────────────────────────────────────┘

Addresses #275 (other plugin commands visual output)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2026-01-28 17:24:49 -05:00

2.0 KiB

Raw Blame History

/check-agent - Validate Agent Definition

Visual Output

When executing this command, display the plugin header:

┌──────────────────────────────────────────────────────────────────┐
│  ✅ CONTRACT-VALIDATOR · Agent Check                              │
└──────────────────────────────────────────────────────────────────┘

Then proceed with the validation.

Validate a single agent's tool references and data flow.

Usage

/check-agent <agent_name> [claude_md_path]

Parameters

agent_name (required): Name of the agent to validate (e.g., "Planner", "Orchestrator")
claude_md_path (optional): Path to CLAUDE.md file. Defaults to ./CLAUDE.md

Workflow

Parse agent definition:
- Locate agent in CLAUDE.md (Four-Agent Model table or Agents section)
- Extract responsibilities, tool references, workflow steps
Validate tool references:
- Check each referenced tool exists in available plugins
- Report missing or misspelled tool names
- Suggest corrections for common mistakes
Validate data flow:
- Analyze sequence of tools in agent workflow
- Verify data producers precede data consumers
- Check for orphaned data references
Report findings:
- List all tool references found
- List any missing tools
- Data flow validation results
- Suggestions for improvement

Examples

/check-agent Planner
/check-agent Orchestrator ./CLAUDE.md
/check-agent data-analysis ~/project/CLAUDE.md

Available Tools

Use these MCP tools:

validate_agent_refs - Check agent tool references exist
validate_data_flow - Verify data flow through agent sequence
parse_claude_md_agents - Parse all agents from CLAUDE.md

2.0 KiB Raw Blame History