create-fixmes
Create FIXME's in the codebase for each of the issues in the given input file.
Best use case
create-fixmes is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Create FIXME's in the codebase for each of the issues in the given input file.
Teams using create-fixmes should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/create-fixmes/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How create-fixmes Compares
| Feature / Agent | create-fixmes | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Create FIXME's in the codebase for each of the issues in the given input file.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
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/<something>/<date>.md", so just move it to ".../_tasks/done/<date>-<something>.md")
Related Skills
create-task-from-json
Create a prompt from a short task description in a JSON file
create-github-issues-from-file
Convert a file containing identified issues into GitHub issues. Use after running identify-* commands to create corresponding GitHub issues.
convert-github-issues-to-fixmes
Convert triaged autoclaude GitHub issues into FIXMEs in the codebase. Use when you want to process issues that have been triaged by authorized users.
writing-specs
Write high quality specifications or design docs for a program. Use any time you are asked to write, improve, or update specs / design docs (e.g., files in a `specs/` folder).
writing-ratchet-tests
Write ratchet tests to prevent accumulation of code anti-patterns. Use when asked to create a "ratchet test" for tracking and preventing specific code patterns (e.g., TODO comments, inline imports, broad exception handling).
writing-docs
Write high quality, user-facing documentation. Use any time you need to write, improve, or update a significant amount of user-facing documentation (e.g., files in a "docs/" folder or README file).
wait-for-agent
Wait for another agent to enter WAITING state, then execute follow-up instructions
update-issues-in-repo
Convert a file containing identified issues into a tracked file in current_tasks/. Use after running identify-* commands to create a local record of current issues.
triage-backlog
Interactively triage the user's local engineering backlog file into GitHub issues. Use when the user wants to process their raw thought notes / ticket backlog into proper GitHub issues.
think-of-something-to-fix
Come up with good ideas about what to fix. Use when you have to fix something, but you're not sure what.
sync-tutorial-to-e2e-tests
Match tutorial script blocks to e2e pytest functions and add missing tests
minds-dev-iterate
Set up and iterate on the minds app stack (desktop client, workspace server, mngr, forever-claude-template) with a running Docker agent