# Fighter Sword

> Use Fighter Sword when the change must run across an entire line — a full sequential chain, pipeline stage, import row, or dependency thread — and anything short of cleaving the whole row leaves the job incomplete.

- Skill: `hmbown/fighter-sword-2` (Agent Skill)
- Install (CLI): `npx skillmds@latest add hmbown/fighter-sword-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/hmbown/fighter-sword-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- License: CC0-1.0
- Author: Hmbown (https://skillmd.com/u/hmbown)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/hmbown/fighter-sword-2

---

# Fighter Sword
Cleave the entire row in one decisive pass.
## What This Skill Does
Use Fighter Sword when the change must run across an entire line — a full sequential chain, pipeline stage, import row, or dependency thread — and anything short of cleaving the whole row leaves the job incomplete.
In this chip pack, Fighter Sword is treated as a metaphorical battle-chip procedure with a shipping-now delivery profile.
Canonical reference input: Fighter Sword.
Hermes shelf: [Direct Fire and Breach](../DESCRIPTION.md).
## When To Use

- A refactor, removal, or edit must span an entire sequential chain or pipeline in one clean pass.
- Partial cuts would leave inconsistencies; the problem extends across the whole row.
- You have surveyed the full length of the target line and can confirm the strike should run edge to edge.

## 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

1. Restate the target, success condition, and no-touch boundaries before you spend the chip.
2. Survey the full row — read every file, function, or stage in the target chain from start to end.
3. Execute the cut across the entire line in one coordinated pass.
4. Verify the row is clean end to end and that adjacent rows were not disturbed.
5. Package the result with concrete evidence, what stayed untouched, and the next recommended chip only if follow-up is truly needed.

## Deliverables

- A complete row-level refactor, removal, or edit applied uniformly across the full chain.
- A summary confirming the cut ran edge to edge with no partial residues left behind.

## Pitfalls / Guardrails

- Keep the metaphor anchored to a real operator move instead of drifting into lore.
- Do not use Fighter Sword when only a local edit is needed — use Sword instead.
- If you cannot see the full length of the row, close distance and read before swinging.
- A full-row cut is committal; if the row contains mixed concerns, split them before sweeping.
- 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
```text
/fighter-sword cleave across an entire row: apply one consistent refactor, removal, or edit spanning the full sequential chain in a single pass, then verify the whole line is clean
```