quick

Apply small, targeted code changes without session protocols or logging.

1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/lasswellt/cc-plugin-suite --skill quick-lasswellt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quick
Source: https://github.com/lasswellt/cc-plugin-suite/tree/main/skills/quick
Command: npx skills add https://github.com/lasswellt/cc-plugin-suite --skill quick-lasswellt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Make targeted changes quickly without the overhead of sprint planning, session setup, or agent coordination.

Core Features & Use Cases

  • No session protocol: operate without formal coordination.
  • No activity feed logging: keep workflows lightweight.
  • No agents: execute directly on a single-file change.
  • Ideal for ad-hoc fixes, typos, and simple config tweaks.

Quick Start

Describe the exact file and change you want, and Quick will apply a small, targeted modification with no ceremony.

Frequently Asked Questions about quick

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

FAQPage Schema
How do I make a quick code change without setting up a full session or logging protocol?

To make a quick code change without session setup, describe the exact file and modification needed. The system applies targeted edits directly, omitting formal coordination and activity logging to enable rapid fixes.

What is the best way to fix typos and apply simple config tweaks across a project?

The best way to fix typos and apply config tweaks is using a lightweight ad-hoc workflow that enforces strict scope boundaries. This prevents wide-reaching changes while allowing rapid single-file edits.

Can I execute ad-hoc code edits directly on a single file without coordinating agents?

Yes, you can execute ad-hoc code edits directly on a single file without coordinating agents. The quick workflow operates without formal session protocols to keep workflows lightweight for small modifications.

Does the quick workflow support wide-reaching refactoring or only strict single-file scope boundaries?

The quick workflow only supports strict single-file scope boundaries. It enforces these limits to avoid wide-reaching changes, making it unsuitable for complex refactoring and ideal only for small, targeted modifications.