# Long Sword

> Use Long Sword when the problem is visible locally but the fix must extend further — across file boundaries, into deeper call stacks, or through intermediary layers that a normal Sword cannot reach.

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

---


# Long Sword

Reach past the first layer and cut through to the real target.

## Overview

Use Long Sword when the problem is visible locally but the fix must extend further — across file boundaries, into deeper call stacks, or through intermediary layers that a normal Sword cannot reach.

This is the secondary Codex compatibility rendering of a metaphorical battle-chip pattern with a shipping-now execution model.

Canonical chip family: Long Sword
Codex shelf: Direct Fire and Breach
Provider target: Codex compatibility surface.

## When To Use

- The symptom is local but the root cause lives one or more layers deeper in the call chain.
- A refactor or fix requires coordinated edits across files that share a common interface or contract.
- You need to trace and sever a dependency that extends beyond the current module boundary.

## Workflow

1. Identify the local surface, then extend reach by tracing imports, callers, or shared types to the true target.
2. Cut through each layer in order — edit the deepest root first, then propagate the fix outward.
3. Verify that the extended strike did not leave orphaned references or broken contracts at any layer.

## Deliverables

- A coordinated multi-file edit that resolves the root cause, not just the surface symptom.
- A map of the reach path: which layers were touched and why the fix could not stay local.

## Guardrails

- Do not use Long Sword when a local Sword cut would suffice — extended reach is for depth, not convenience.
- If the fix requires changes across more than three files or modules, consider whether a broader chip is more appropriate.
- Never extend reach speculatively; trace the dependency chain first and confirm the true target.

## Default Invocation

Use Long Sword to trace the problem past the local surface and cut through to the root cause: edit the deepest layer that needs to change, then propagate the fix outward, verifying each layer stays intact.