In this article
prompt-refactor
| Field | Value |
|---|---|
| Kind | skill |
| Source | .github/skills/hve-core/prompt-refactor |
| Invocation | Invoked directly as /prompt-refactor, or loaded on demand by referencing agents |
| Interactive | No |
What it does
Compatibility alias for behavior-preserving prompt artifact cleanup. Routes refactoring to hve-builder refactor mode.
When to use it
Use this compatibility alias to simplify existing customization artifacts while
preserving their triggers, outputs, safety boundaries, and required behavior.
It maps promptFiles to HVE Builder's refactor mode and shares its quality gates.
Use prompt-builder when behavior must intentionally change or a new artifact is
needed; use prompt-analyze when source must remain read-only.
Example usage
Ask: /prompt-refactor promptFiles=.github/prompts/sample/report.prompt.md requirements=Consolidate repeated output instructions while preserving section order, citation requirements, missing-data handling, and approval gates. Edit only this file. Supply the actual existing prompt and its consumers as context.
Expect the baseline contract to guide a coherent cleanup, followed by HVE Builder validation and its review pass. The current workflow contract resolves the review verdict and overall outcome; the alias does not add another review loop.
Success is less duplication without lost capabilities, with changed files, rationale, verdicts, and evidence reported separately. A proposed artifact split, type change, or new support file requires renewed scope approval. Shorter prose alone is not success if it removes a stop condition or required behavior.