quick

Execute small code changes across 1-3 files without planning.

4|Updated Mar 24, 2026

Search Tags:#automation #git #commit #quick #code-edit #small-change #no-plan

Ready to run

npx skills add https://github.com/skaisser/blueprint --skill quick-skaisser

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: quick
Source: https://github.com/skaisser/blueprint/tree/main/skills/quick
Command: npx skills add https://github.com/skaisser/blueprint --skill quick-skaisser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Minor changes can block momentum when a full planning workflow is unnecessary; this skill enables fast, targeted edits without assembling a plan.

Core Features & Use Cases

Lightweight change execution for 1-3 file edits.
Optional GitHub Issues integration to associate changes with issues.
Deterministic, minimal-diff commits that keep history clean.

Quick Start

Ask for a small change and commit it immediately, without planning.

Frequently Asked Questions about quick

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

FAQPage Schema

How do I make small code edits without triggering a full planning workflow?▼

Make small code edits without a planning workflow by using a fast, single-purpose execution path designed for 1-3 file adjustments. It applies targeted changes directly and uses a minimal-diff commit to keep history clean.

What is the best way to commit minor refactors and typo fixes quickly?▼

The best way to commit minor refactors quickly is using a deterministic, minimal-diff commit process. It creates a clean patch for small changes without assembling a plan, ensuring your repository history stays uncluttered.

Can I associate small config updates with a GitHub Issue?▼

Yes, you can associate small config updates with a GitHub Issue. The fast change execution workflow supports optional GitHub Issue context, allowing you to link targeted code edits directly to existing issues in your repository.

When should I avoid using a no-plan workflow for code changes?▼

You should avoid a no-plan workflow for code changes that require modifying more than 1-3 files or involve complex logic. This approach is strictly for minor edits like typo fixes and small refactors, lacking the planning needed for larger features.