Menu
Create FIXME's in the codebase for each of the issues in the given input file.
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
Address review comments on a pull request -- apply CLAUDE:/SCULPTOR:-prefixed instructions, and critically evaluate feedback from automated reviewers (Vet, Copilot, or any bot)
Prune code comments down to what helps future maintainers. Reviews comments on the current branch's diff and removes incidental history, defensive justification, and correctness arguments. Invoke with /crispy-comments.
End-to-end dev workflow for the minds app stack -- first-time bring-up, every-startup vendor/mngr sync, and the iteration loop against a running Docker agent. Use this when starting or restarting the dev Electron app, or after changing any minds component (mngr, the system interface, the default workspace template).
Create a new PRIVATE GitHub repo that is a full-history copy of imbue-ai/default-workspace-template's current main branch, clone it to <parent-dir>/<repo-name> (default $HOME/project), and push. Use when the user asks to "spin up a new default-workspace-template clone", "fork the default-workspace-template as a private repo", "make me a new private copy of default-workspace-template", or similar.
Use the root justfile as the canonical entry point for ANY minds task -- minds app (desktop client), pool hosts, minds environments (activate/deploy/destroy), minds deployments, and minds tests. Before running ad-hoc `uv run minds ...` / `mngr imbue_cloud ...` commands, check the justfile for a named recipe; if none exists for the task, ADD one. Use whenever the request involves the minds app, pool/leased hosts, a minds env/tier (dev/staging/production), or a minds deploy.
Cut a new production release of the minds app (version bump, FALLBACK_BRANCH, vendor/mngr sync, and minds-v<version> tags on both mngr and default-workspace-template, proven green on CI). The full procedure lives in apps/minds/docs/release.md in the mngr checkout; this skill defers to it. Use when the user asks to "release a new version of minds", "cut a minds release", "bump the minds version", "update the vendored mngr in default-workspace-template", or anything of that shape.
| name | create-fixmes |
| argument-hint | ["input_file"] |
| description | Create FIXME's in the codebase for each of the issues in the given input file. |
Your task is to create "# FIXME:" comments in the codebase for each of the issues listed in this file: $1
My decisions about what to do for each issue are in the "decision" section. If it says "ignore", then do nothing for that issue.
Make exactly ONE "# FIXME:" comment per issue (that I accepted). It should contain all of the necessary context about the issue and what to fix (both in the particular instance the FIXME is near, and whether other similar instances should be fixed too)
In order to figure out the best single place for the FIXME comment, first go gather all of the context for the relevant library (per instructions in CLAUDE.md).
Then think carefully about where the best place is to put the FIXME comment for each issue, and what exactly should be expressed in each issue. If the FIXME applies to more than just this one instance, be clear about that in the description, but do NOT make multiple FIXME comments for the same issue.
After that, go ahead and insert the FIXME comments in the appropriate places in the codebase. Remember that multi-line descriptions should have their subsequent lines have TWO spaces (ie, " ") after the "#" character, not just one
Once the comments have been added, commit.
Finally, move $1 to the "done" folder (the path ends in ".../_tasks//.md", so just move it to ".../_tasks/done/-.md")
