cquick

Solid

Quick fix with TDD — no spec/review for small changes. Branch, test, implement, commit.

Code & Development 61 stars 2 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 88/100

Stars 20%
60
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# /cquick — Quick Fix with TDD > **Shared constraints apply.** Before executing, read `_shared/constraints.md` from the parent of this skill's base directory. All constraints there apply to this skill. You are the quick-fix agent. Your job is to implement a small, focused change using TDD without the full Correctless ceremony. No spec, no review, no verify, no docs — just branch, write test, implement, verify tests pass, and commit. ## Before You Start ### Branch Guard Check the current branch: ```bash git branch --show-current ``` If on `main` or `master`, stop immediately and tell the user: "You're on the main branch. Create a feature branch first: `git checkout -b fix/short-description`." Do not auto-create branches — the human decides the branch name. ### Active Workflow Guard Check if a workflow is already active on this branch: ```bash .correctless/hooks/workflow-advance.sh status 2>/dev/null ``` If a workflow is active, stop and tell the user: "There's an active Correctless workflow on this branch. Use the workflow skills (`/ctdd`, `/cverify`, etc.) instead of `/cquick`. This skill is for standalone small fixes outside of an active workflow." ## Scope Guard Before writing any code, assess the change: - If the change will exceed 50 LOC (lines of code) or touch more than 3 files, stop and say: "This is bigger than a quick fix — run `/cspec` to start the full workflow." - Re-evaluate during implementation. If you realize mid-way that the change is growing beyon...

Details

Author
joshft
Repository
joshft/correctless
Created
2 months ago
Last Updated
yesterday
Language
Shell
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Testing & QA Solid

ctdd

Enforced TDD workflow. Write failing tests from spec rules, then implement. Use after /creview approves a spec.

61 Updated yesterday
joshft
AI & Automation Listed

quick-fix

Fast workflow for small changes, bug fixes, and UI tweaks that don't require full feature development. Uses sub-agent orchestration with model selection (Sonnet 4.5 orchestrator, Haiku 4.5 workers) for efficient context management. Handles styling adjustments, minor functionality fixes, and quick improvements while maintaining project quality standards.

3 Updated today
Hildegaardchiasmal966
Testing & QA Solid

tdd

Write code through a disciplined, BDD-framed Test-Driven Development loop: build a behavior test list, then drive each behavior through red-green-refactor with an enforced observed-failure gate. Use when the user wants to implement, build, or write code test-first, "do TDD", follow "red-green-refactor", drive code from tests, or grow a feature behavior-by-behavior with tests leading. This skill writes and changes code; it does not produce a test plan document (use test-planning), review or audit existing code (use code-review), specify what a feature should do (use plan-a-feature), or find the root cause of a bug (use investigate).

69 Updated 2 days ago
testdouble
Code & Development Solid

crefactor

Structured refactoring with behavioral equivalence enforcement. Tests must pass before AND after. Any test change requires explicit approval. Writes characterization tests for low-coverage code.

61 Updated yesterday
joshft
Web & Frontend Solid

phxquick

Implement small Phoenix changes without planning — add validations, update routes, fix components, create migrations. Use for single-file edits under 50 lines.

384 Updated 4 days ago
oliver-kriska