skills.rest
joshft
joshftCOMMUNITY
Explore all skills by this author →
GitHub

cquick

Apply a strict TDD workflow to isolated bug fixes on feature branches.

65|2|Updated Mar 27, 2026
Search Tags:#tdd#branching#software-engineering#bugfix#tests#quick-fix
One-click install
npx skills add https://github.com/joshft/correctless --skill cquick
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cquick
Source: https://github.com/joshft/correctless/tree/main/correctless/skills/cquick
Command: npx skills add https://github.com/joshft/correctless --skill cquick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables fast, isolated bug fixes by following a strict TDD workflow, avoiding the full Correctless ceremony for small changes.

Core Features & Use Cases

  • TDD-driven fixes: write a failing test first, then implement the minimal change to satisfy it.
  • Lightweight lifecycle: branch, test, implement, and commit without specs or reviews.
  • Scope constraints: designed for changes under 50 LOC and within 3 files to keep quick fixes focused.

Quick Start

Start by creating a feature branch, write a failing test, implement the fix, run the tests, and commit when they pass.

Frequently Asked Questions about cquick

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

FAQPage Schema
How do I apply TDD for a quick bugfix without full code review ceremonies?▼

A TDD-guided quick bugfix enforces writing a failing test first, implementing minimal code to pass it, and committing on a feature branch without specs or reviews. This lightweight lifecycle keeps small, self-contained changes focused and fast.

What is the best way to isolate small software engineering fixes using test-driven development?▼

The best way to isolate small fixes is using a strict TDD workflow on a dedicated feature branch. You write a failing test, confirm the failure, implement the minimal change, run tests, and commit, bypassing heavy stakeholder approval processes.

Can I use a quick-fix TDD workflow for larger changes spanning multiple files?▼

No, this quick-fix TDD workflow is constrained to changes under 50 lines of code and within 3 files. It is designed for small, self-contained bug fixes where full specification and review ceremonies are unnecessary.

When do I need to use a lightweight branching workflow for bug fixes?▼

You need a lightweight branching workflow when applying rapid, isolated bug fixes that require quick turnaround without stakeholder approval. It allows you to branch, test, implement, and commit quickly while maintaining TDD integrity.

Does the TDD quick-fix workflow require any external testing dependencies?▼

No external dependencies are required. The workflow operates by enforcing the TDD cycle internally: write a failing test first, implement minimal code to satisfy it, run tests, and commit within the quick-fix limits.

Related Skills

Explore More Software Engineering Skills→
mycelium-iomycelium-io
112

tdd

Execute test-driven development workflows through red-green-refactor cycles.

Official
Intermediate
doravidandoravidan

ralph-merge

Merge RALPH worktree changes into the main branch with optional squash.

Community
Basic
NabilThangeNabilThange
1

lint-and-validate

Automate linting and static analysis for Node.js, Python, and TypeScript code.

Community
Intermediate
elsolalelsolal
1

quick-fix-workflow

Automate minimal bug fixes within 3 files and 50 lines with lint, typecheck, and test validation.

Community
Intermediate