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.
Best use case
think-of-something-to-fix is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Come up with good ideas about what to fix. Use when you have to fix something, but you're not sure what.
Teams using think-of-something-to-fix 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/think-of-something-to-fix/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How think-of-something-to-fix Compares
| Feature / Agent | think-of-something-to-fix | 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?
Come up with good ideas about what to fix. Use when you have to fix something, but you're not sure what.
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
# Thinking of something to fix This skill provides guidelines for coming up with good ideas for things to fix. ## What types of things are good to fix? The following are attributes of good fixes for you to tackle: - The issue is obviously a problem (ex: a FIXME or TODO in the codebase, failing test, or something that is otherwise pretty clearly broken). - It's better to fix existing functionality and clean things up than it is to add new features. - The issue should be relatively small and easy to fix and self-contained (eg, not requiring a huge refactor or redesign of the system). - There should be little ambiguity about whether this is something to fix, or how to fix it. - Worst case, fixing style violations, adding additional tests, or updating outdated comments are always good options.
Related Skills
fix-something
Fix a random FIXME in the codebase (in the given scope, use "." for the whole codebase)
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.
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
message-agent
Send a message to another mngr agent. Use when you need to communicate with a peer agent.
identify-style-issues
Identify divergences from the style guide in the $1 library
identify-outdated-docstrings
Identify outdated docstrings in the $1 library