Menu
Capture a quick-fix as a markdown file in the workflow inbox. Use when the user wants to log a trivially scoped mechanical change for later.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Capture a bug report as a markdown file in the workflow inbox. Use when the user wants to log, note, or save a bug for later.
Capture an idea as a markdown file in the workflow inbox. Use when the user wants to log, note, or save an idea for later.
Scaffold a new planning output format adapter. Creates a format directory with all required files implementing the output format contract.
| name | workflow-log-quickfix |
| description | Capture a quick-fix as a markdown file in the workflow inbox. Use when the user wants to log a trivially scoped mechanical change for later. |
| allowed-tools | Bash(mkdir -p) |
This skill captures a quick-fix and writes it to the inbox.
If there's already conversation context about a mechanical change, synthesise it straight into the file without asking questions. If this is a cold start, ask what needs changing and have a natural back-and-forth to draw out the scope. Recognise when it has enough detail (typically 1-3 exchanges) and wrap up.
Capture only โ these are rules, not guidelines:
When ready, generate a short kebab-case slug from the core change (e.g., replace-interface-with-any, update-deprecated-api) and write the file:
mkdir -p .workflows/.inbox/quickfixes
File: .workflows/.inbox/quickfixes/{YYYY-MM-DD}--{slug}.md (use today's actual date)
Confirm with a one-liner:
Output the next fenced block as a code block:
Logged quick-fix: {slug}