fixer

Apply exact code changes to specified files and report a completion summary.

2|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/302ai/302-coding-plugins --skill fixer-302ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fixer
Source: https://github.com/302ai/302-coding-plugins/tree/main/plugins/oh-my-claudecode/skills/fixer
Command: npx skills add https://github.com/302ai/302-coding-plugins --skill fixer-302ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fast, focused implementation for well-defined tasks that require quick delivery of reliable code without research or planning.

Core Features & Use Cases

  • Fast, deterministic execution of clearly specified requirements.
  • Reads provided context and existing files before editing to ensure precise changes.
  • Handles repetitive edits and bug fixes across multiple files with consistent results.

Quick Start

Execute the clearly specified task with complete context, delivering a complete implementation without additional research or planning.

Frequently Asked Questions about fixer

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

FAQPage Schema
How do I execute clearly defined coding tasks without extra planning steps?

To execute clearly defined coding tasks without planning, provide exact change descriptions and complete context. The implementation reads existing source files first, applies deterministic edits, and reports a concise completion summary without performing additional research.

What is the best way to apply repetitive bug fixes across multiple files consistently?

The best way to apply repetitive bug fixes across multiple files is to specify exact changes with full context. This ensures deterministic execution and consistent results by reading source files before editing, avoiding autonomous planning or research steps.

Can I use this approach for tasks that require extensive research and architecture planning?

No, you cannot use this approach for tasks requiring research or architecture planning. It is designed strictly for well-scoped, independent tasks that can be completed by editing a small set of files based on provided context.

How do I ensure precise code implementation when making well-scoped edits?

To ensure precise code implementation for well-scoped edits, provide complete context and exact change descriptions. The process relies on reading existing source files before applying deterministic edits, guaranteeing accurate modifications without guessing.

Does this deterministic execution method work with incomplete task specifications?

No, deterministic execution does not work with incomplete task specifications. It requires clearly specified requirements and provided context to deliver fast and focused implementation, as it does not perform independent research to fill in missing details.

Why does my bug fix execution include unwanted planning steps before editing?

Unwanted planning steps occur if the execution method is not scoped for fast implementation. This approach skips research entirely, adhering to constraints of reading source files before editing and relying strictly on provided context for deterministic code changes.