Menu
Output lists of locations as vim quickfix lists.
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
| name | vim-quickfix |
| description | Output lists of locations as vim quickfix lists. |
| allowed-tools | Bash(mkdir -p .qf), Write(.qf/*), Edit(.qf/*) |
| disable-model-invocation | true |
!mkdir -p .qf
For entries that reference files in the working tree, write a plain quickfix file.
File: .qf/<task-name>.txt
Format: file:line:col:message (one per line, col can be 0 if unknown)
src/foo/bar.clj:42:0:TODO: fix this
src/foo/baz.clj:10:5:suspicious pattern
Tell the user: :cfile .qf/<task-name>.txt
For entries that reference files at specific commits (e.g. reviewing TODOs across
a branch's history), write a .vim script that calls setqflist() with full
fugitive URIs.
File: .qf/<task-name>.vim
Use git rev-parse --git-dir — this returns the correct path in both normal repos
and worktrees.
Fugitive requires full 40-character SHAs
git rev-parse <short-or-ref>
fugitive://<git-dir>//<full-40-char-sha>/<path-from-repo-root>
Example:
fugitive:///Users/bob/code/repo/.git/worktrees/my-branch//abc123...def/src/foo.clj
The display formatter lives at ./fugitive-qf.vim and
defines g:SkillQfFugitiveText which strips fugitive URIs to 7b4a70a:path in the
quickfix window. Source it first, then just emit the setqflist call:
source /absolute/path/to/skills/vim-quickfix/fugitive-qf.vim
let s:g = 'fugitive://<git-dir>//'
call setqflist([], ' ', {
\ 'title': '<descriptive title for the list>',
\ 'quickfixtextfunc': 'g:SkillQfFugitiveText',
\ 'items': [
\ {'filename': s:g . '<full-sha-1>/src/foo.clj', 'lnum': 42, 'text': 'TODO: fix this'},
\ {'filename': s:g . '<full-sha-2>/src/bar.clj', 'lnum': 10, 'text': 'TODO: different commit'},
\ ]})
copen
Use a let variable for the git dir prefix to avoid repeating it on every line.
The ' ' (space) action creates a new list rather than replacing the current one,
so previous quickfix lists are preserved in the stack (:colder to go back).
Tell the user: :source .qf/<task-name>.vim
:cfile):source)HEAD as the commitUse when drafting, writing, or filing a Linear ticket/issue, or asked for a Linear title/body/description.
Use when drafting, writing, or opening a pull request (gh pr create), or asked for a PR title/body/description.
Writing voice for authored prose — PR bodies, Linear tickets, review comments, commit messages.
Hand a file to the user's running editor and block until they finish editing it. Use whenever a draft (PR body, ticket, commit message, any generated file) needs the user's review before you act on it, or when a task says "open this in my editor/vim/nvim".
Clojure style guidelines. Activate before writing or editing Clojure code
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design.