/hypr:validate

Validate that a generated agent correctly reflects your project patterns.

Usage

/hypr:validate planning /hypr:validate frontend /hypr:validate backend /hypr:validate all

Aliases: /hypr:check, /hypr:verify

Checks

For each rule in the agent file, validation runs four checks:

  • Specificity — Is the rule specific to this project? Does it cite real file paths and examples?
  • Accuracy — Does the pattern actually exist in the codebase? Any counter-examples?
  • Completeness — Are there patterns in the code that aren't covered by any rule?
  • Currency — Do referenced files still exist? Has the pattern changed since assessment?

Output

A markdown report containing:

  • Summary — total rules, valid rules, issue counts, coverage percentage
  • Issues — each problematic rule with issue type (Inaccurate / Outdated / Incomplete / Too Generic), supporting evidence, and a suggested fix
  • Missing Patterns — patterns observed in the code that aren't documented
  • Recommendations — what to do next

After Validation

  • Few issues — manually update the rules in the agent file.
  • Many issues — run /hypr:refresh to re-assess the affected aspects.
  • Major drift — re-run the relevant /hypr:assess-* command.

Related Commands