| name | step-sword |
| description | Use Step Sword when the target is identifiable but not within easy reach: you know exactly what needs cutting, but reaching it requires navigating across files, modules, or abstraction layers. Warp directly to the target and make the edit in a single committed action. |
| version | 0.1.0 |
| author | mmbnchips |
| license | CC0-1.0 |
| compatibility | Hermes Agent skills system |
| metadata | {"hermes":{"tags":["shipping-now","metaphorical","direct-fire-and-breach","direct-fire","offense","breach","decisive-action"],"homepage":"https://github.com/Hmbown/mmbnchips"}} |
Step Sword
Close the gap and cut in one motion.
What This Skill Does
Use Step Sword when the target is identifiable but not within easy reach: you know exactly what needs cutting, but reaching it requires navigating across files, modules, or abstraction layers. Warp directly to the target and make the edit in a single committed action.
In this chip pack, Step Sword is treated as a metaphorical battle-chip procedure with a shipping-now delivery profile.
Canonical reference input: Step Sword.
Hermes shelf: Direct Fire and Breach.
When To Use
- You can name the exact remote location that needs editing but it is not adjacent to your current context.
- The problem is well-scoped but buried behind layers of indirection or deep file paths.
- Traversing the full path step by step would waste rounds; the target is clear enough to strike immediately.
Prerequisites
- These procedures rely on the normal tools already present in the active Hermes runtime; this repo does not ship a separate integration layer.
Procedure
- Restate the target, success condition, and no-touch boundaries before you spend the chip.
- Identify the remote target precisely — file path, line range, symbol — so the warp lands cleanly.
- Jump directly to the target context and cut in the same motion.
- Verify the strike from both ends: confirm the edit is correct and that no caller or dependant was sheared.
- Package the result with concrete evidence, what stayed untouched, and the next recommended chip only if follow-up is truly needed.
Deliverables
- A precise remote edit made by direct navigation, not incremental traversal.
- A short note confirming the warp destination and what was left untouched along the path.
Pitfalls / Guardrails
- Keep the metaphor anchored to a real operator move instead of drifting into lore.
- Do not use Step Sword if you cannot name the target precisely — vague warp destinations cause collateral cuts.
- If the path to the target contains other problems that should be addressed first, use a room-control chip instead.
- Do not chain Step Swords to simulate traversal; that is a sign the wrong chip is equipped.
- Keep the chip metaphor anchored to a real operating move; do not let flavor substitute for procedure.
Verification
- Check that the response includes every promised deliverable and leaves an inspectable audit trail.
- Check that confirmed facts, assumptions, and proposed follow-up are visibly separated.
- Check that the metaphor still maps cleanly to a real operator mechanism.
Example Invocation
/step-sword warp directly to the identified remote target and make the precise edit in one committed action, then verify that the change is correct and nothing along the path was disturbed
