quick
/quick
Zero-ceremony atomic task execution. Use for tiny fixes or enhancements (minutes, not hours) that don't warrant SDLC ceremony. Flags: --discuss (disambiguate first), --full (delegate to /pre-commit after execution), --issue N (link commit to GitHub issue).
- Author
- matteocervelli ↗
- Repository
- llms ↗
- Licence
- MIT
- Last repository change
- 21.05.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 21.05.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Zero-ceremony atomic task execution. Use for tiny fixes or enhancements (minutes, not hours) that don't warrant SDLC ceremony. Flags: --discuss (disambiguate first), --full (delegate to /pre-commit after execution), --issue N (link commit to GitHub issue).
Original author description
Zero-ceremony atomic task execution. Use for tiny fixes or enhancements (minutes, not hours) that don't warrant SDLC ceremony. Flags: --discuss (disambiguate first), --full (delegate to /pre-commit after execution), --issue N (link commit to GitHub issue).
How it works
- Purpose
- When to Use vs Other Skills
- Usage
- Workflow
- Constraints
- Tracking: quick-tasks.md
- Tips
SKILL.md preview
--- name: quick description: "Zero-ceremony atomic task execution. Use for tiny fixes or enhancements (minutes, not hours) that don't warrant SDLC ceremony. Flags: --discuss (disambiguate first), --full (delegate to /pre-commit after execution), --issue N (link commit to GitHub issue)." --- # Quick Skill ## Purpose Atomic task execution without SDLC ceremony. Fills the gap between "raw Claude" and `/fix`/`/implementation`: - No opusplan model switch - No task list creation - No TDD by default - No PR creation - Issue GitHub optional Use when a change takes minutes, not hours. ## When to Use vs Other Skills | | `/quick` | `/fix` | `/implementation` | | -------------- | -------------- | ----------------- | -------------------- | | Ceremony | None | Minimal | Full (TDD, opusplan) | | Size | Tiny (minutes) | Small-medium | Medium-large | | Type | Anything | Bug / tech debt | Feature / refactor | | Issue required | No | No | No | | PR created | No | Optional (`--pr`) | Yes | | Tests required | No | Regression only | Full TDD | ## Usage ```bash /quick fix the failing auth test /quick --discuss add rate limiting to the API # disambiguate before executing /quick --full refactor the user service # run /pre-commit after execution /quick --issue 42 update error message # link to GitHub issue in commit ``` ## Workflow ### Bare mode (default) 1. **Snapshot** — Run `git status` and `git branch --show-current` to establish context 2. **Execute** — Implement the minimal change - Trivial edit (1-2 files): work on current branch - Slightly larger: `git checkout -b <type>/brief-description` 3. **Smoke tests** — After executing, always output a short checklist (3–5 items) the user can run manually before committing. Infer from modified files: - REST endpoint → `curl` commands (happy path + one error case) - Frontend → numbered browser steps - CLI → shell commands - Library/module → `python -c "..."` one-liner 4. **Gate** — Run `/security-verify scan` before committing (non-negotiable per `rules/security-gate.md`) 5. **Commit** — Atomic commit with conventional-commits message: - With issue: `fix: <description>` + `Fixes #42` in commit body - Without issue: `fix: <description>` or `feat: <description>` 6. **Review suggestion** — After committing, always suggest: > "Run `/review changes` to get a companion second opinion before moving on." 7. **Track** — Append entry to `.claude/memory/local/quick-tasks.md` ### --discuss mode Before executing: 1. Ask 2-3 targeted disambiguation questions (scope, approach, edge cases) 2. Save decisions to `.claude/memory/local/CONTEXT.md` 3. Proceed with bare mode ### --full mode After executing: 1. Delegate to `/pre-commit` (quality + tests + security + changelog) 2. Use this when the change touches logic where regression is a real risk ## Constraints - Stay on current model — no `/model opus` suggestion - No `TaskCreate` calls - No TDD unless `--full` flag - No `gh pr create` — use `/fix` or `/implementation` if a PR is needed - Security scan always mandatory before commit ## Tracking: quick-tasks.md After each execution, append to `.claude/memory/local/quick-tasks.md`: ```markdown ### YYYY-MM-DD HH:MM — <task description> - Branch: <branch-name> or "current branch (no new branch)" - Commit: <sha> "<message>" - Mode: bare | discuss | full - Issue: #N or — ``` File is session-scoped and gitignored (`memory/local/` is never committed). ## Tips - If the change grows beyond ~30 minutes of work, switch to `/fix` or `/implementation` - `--discuss` is especially useful when the task is ambiguous or touches multiple areas - `--full` is for logic changes (not just config/text) where test coverage matters
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · matteocervelli/llms | 100 | MIT |
| rizukirr/vibekit | 100 | MIT |
| pe-menezes/vibeflow | 100 | MIT |
| oliver-kriska/claude-elixir-phoenix | 100 | MIT |
| pg013c/pg-toolkit | 90 | MIT |
| marcushyett/tik-test | 84 | MIT |
| AO-Cyber-Systems/devflow-claude | 82 | MIT |
| alexandrbasis/claudops | 81 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 5116124b606a (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95Commit
Create a conventional-format commit, push, and open a GitHub PR that links the Jira ticket. GitHub is the source of record. Reuses buddy's SourceControl for commit formatting when available. USE WHEN sdlc commit, commit, create commit, open PR, push and PR, ship it, create pull… - 100quick-fix
Express lane for trivial bugs and tiny changes — skips the full contract ceremony. Use for one-line fixes, copy/CSS tweaks, config changes, dependency bumps, or any change localized to one root cause with no new behavior, instrumentation, schema, or platform. Triggered by `/fix… - 82gsd-quick
Use when the user wants a small, ad-hoc change handled with GSD guarantees (atomic commits, STATE.md) but without the full pipeline. Tasks land in .planning/quick/; --full, --discuss, --research, --validate add the skipped agents back. - 100ship-it
Code commit, PR creation, merge, and issue closure workflow via GitHub CLI (gh). Triggers after a goal (GitHub Issue) implementation is complete — commit code, push branch, create PR, merge, then close the issue. Use when the user says "提交代码", "commit and merge", "创建PR", "合入",… - 100commit
Write a commit message and create a git commit. Use when the user wants to commit changes, asks for a commit message, or says "commit this" or "make a commit". - 100pre-commit-quality-review
Use when the user asks to commit, amend, or squash code, or requests a pre-commit structural quality review.