forge-quick

Automate small code changes across 1-3 files with test and lint validation.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/whatwecando/tombola --skill forge-quick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge-quick
Source: https://github.com/whatwecando/tombola/tree/main/.claude/skills/forge-quick
Command: npx skills add https://github.com/whatwecando/tombola --skill forge-quick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quick, targeted changes often require full CI/CD pipelines; this skill enables fast local edits and minimal orchestration for small changes.

Core Features & Use Cases

  • Targeted changes: make small edits with minimal scope.
  • Minimal orchestration: avoids running the full pipeline; quick validation.
  • Use Case: ideal for minor bug fixes or tweaks across a couple files without heavyweight processes.

Quick Start

Describe the change you want to apply, then invoke the quick agent to implement it.

Frequently Asked Questions about forge-quick

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

FAQPage Schema
How do I apply quick fixes to code without triggering a full CI/CD pipeline?

To apply quick fixes without full CI/CD pipelines, automate small targeted code changes across 1-3 files. This approach uses minimal orchestration for minor bug fixes or tweaks, requiring only local linting and tests for validation.

What is the best way to automate minor bug fixes across a couple of files?

The best way to automate minor bug fixes across a couple files is using minimal orchestration for targeted code changes. Provide a clear change description and identify the affected files to implement small tweaks without heavyweight processes.

Can I use targeted code changes for small refactors without running the full pipeline?

Yes, you can use targeted code changes for small refactors without running the full pipeline. This method is designed for 1-3 files, applying small edits with minimal scope and validating via quick tests and linting after changes.

What do I need to provide to automate a small code change?

To automate a small code change, you need to provide a clear description of the change and identify the affected files. Validation via tests and linting is then required after the changes are applied to ensure correctness.

When should I avoid using minimal orchestration for code edits?

You should avoid using minimal orchestration for code edits when changes span more than 1-3 files or require full pipeline orchestration. It is specifically designed for minor feature tweaks, quick bug fixes, and small refactors with minimal scope.

How does quick validation work for small code tweaks?

Quick validation for small code tweaks works by running tests and linting immediately after applying targeted changes. This bypasses full pipeline orchestration, enabling fast local edits and minimal validation for minor bug fixes.