festina-quick

Automate minimal-change code fixes with a single-commit workflow.

1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/mattfletcher94/festinalente --skill festina-quick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: festina-quick
Source: https://github.com/mattfletcher94/festinalente/tree/main/apps/festinalente/src/content/skills/festina-quick
Command: npx skills add https://github.com/mattfletcher94/festinalente --skill festina-quick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables fast implementation for simple tasks with minimal Q&A, reducing overhead for small fixes and config changes by guiding a concise, single-commit workflow.

Core Features & Use Cases

  • Minimal Q&A: problem, done, and quick context without multi-step planning.
  • Optional research: ability to scan the codebase for context before implementing.
  • Structured quick task artifacts: stores progress in .festinalente/quick/{id}/quick.xml and a deterministic quick-id.
  • Optional documentation updates after changes.

Quick Start

Describe a small change you want implemented and start the quick flow to generate a quick task and commit it in a single branch.

Frequently Asked Questions about festina-quick

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

FAQPage Schema
How do I automate small code fixes and configuration changes in a single commit?

Small code fixes and configuration changes are automated through a guided Q&A workflow that gathers problem context and implements minimal changes in a single commit. This approach reduces overhead for simple tweaks without multi-step planning.

What is the best way to implement minor features without multi-step planning overhead?

Minor features can be implemented using a minimal Q&A workflow that asks only for the problem, completion criteria, and quick context. This avoids multi-step planning and applies small tweaks across codebases with a single commit.

Can I use this workflow to scan my codebase for context before implementing a quick fix?

Codebase scanning for context is supported as an optional research step before implementing quick fixes. This allows the workflow to gather relevant context from the codebase prior to applying minimal changes.

Does this single-commit task workflow store progress artifacts in XML format?

Progress artifacts are stored deterministically as XML files in a dedicated directory. Each task generates a quick.xml artifact stored under a specific quick-id folder structure for tracking.

How do I update documentation after applying minor code tweaks?

Documentation updates are optionally applied after implementing minor code tweaks. The workflow can automatically update docs following the single-commit implementation of small fixes and configuration changes.

When should I avoid using a minimal-change single-commit workflow for task implementation?

This minimal-change workflow should be avoided for complex tasks requiring multi-step planning or extensive codebase modifications. It is designed for small tweaks, configuration changes, and minor features that fit within a single commit.