/hypr:refresh
Re-run an assessment to update an existing agent with evolved codebase patterns.
Usage
/hypr:refresh planning /hypr:refresh frontend /hypr:refresh backend /hypr:refresh all
Aliases: /hypr:update, /hypr:sync
When to Refresh
- Significant new features have been added
- Coding conventions have changed
- New patterns have emerged
- /hypr:validate reported many issues
- Team members report agent suggestions don't match current patterns
Process
- Backup the existing agent to
[agent-type]-agent.backup.md. - Compare current code against the existing rules — identify new, changed, deprecated, and stable patterns.
- Re-assess only the changed aspects rather than running the full assessment again.
- Merge updates: keep stable rules, update changed rules, add new rules, remove deprecated ones.
- Validate with /hypr:validate.
Refresh vs. Full Re-Assessment
| Scenario | Action |
|---|---|
| Minor pattern changes | Use /hypr:refresh |
| Major architecture change | Re-run full assessment |
| New technology added | Re-run full assessment |
| Few validation issues | Use /hypr:refresh |
| Many validation issues | Re-run full assessment |
| Regular maintenance | Use /hypr:refresh |
Related Commands
- /hypr:assess — full re-assessment
- /hypr:validate — verify agent accuracy