fighter-sword

Apply a single coordinated change across an entire row or pipeline.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Hmbown/mmbnchips --skill fighter-sword
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fighter-sword
Source: https://github.com/Hmbown/mmbnchips/tree/main/generated/codex/fighter-sword
Command: npx skills add https://github.com/Hmbown/mmbnchips --skill fighter-sword

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Executes a full-row refactor across an entire line, ensuring a single cohesive change across the entire sequence so nothing is left partial or inconsistent.

Core Features & Use Cases

  • Single-pass row edits: Apply a uniform change across the entire row, pipeline segment, or dependency chain.
  • End-to-end consistency: Guarantees the entire sequence remains coherent after the edit.
  • Safe, scoped application: Avoids partial edits by requiring the full row to be addressed in one operation.

Quick Start

Describe the full-row change you want across the entire line and the system will apply it in one coordinated pass.

Frequently Asked Questions about fighter-sword

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I refactor an entire pipeline in a single pass without leaving partial edits?

To execute a single-pass refactor across an entire row, you describe the full-row change and the system applies it in one coordinated operation. This guarantees end-to-end consistency by ensuring no partial edits remain in the pipeline.

What is a full-row refactor and when do I need it for my workflow?

A full-row refactor is a single coordinated change applied across an entire line or dependency chain. You need it when changes must span the entire pipeline, ensuring no partial edits or inconsistent states remain.

Can I use a single-pass refactor for end-to-end consistency across a dependency chain?

Yes, you can use it to apply a uniform change across an entire dependency chain. It guarantees end-to-end consistency by requiring the full row to be addressed in one operation, avoiding partial edits.

What's the best way to ensure safe, scoped application when editing a pipeline segment?

The best way to ensure safe, scoped application is to apply a uniform change across the entire pipeline segment in one pass. This avoids partial edits by requiring the full row to be addressed.

Why does my pipeline refactor leave partial edits or inconsistent states?

Your pipeline refactor leaves partial edits because the full row was not addressed in a single coordinated change. Applying the edit across the entire sequence in one operation ensures end-to-end consistency.