imbue-ai.

latchkey

Interact with third-party or self-hosted services (Slack, Google Workspace, Dropbox, GitHub, Linear, Coolify...) using their HTTP APIs on the user's behalf.

asciinema-demos

Create 1-3 short asciinema demo recordings (5-20 seconds each) that demonstrate completed work. Use only when explicitly instructed to create demos.

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.

create-fixmes

Create FIXME's in the codebase for each of the issues in the given input 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.

create-task-from-json

Create a prompt from a short task description in a JSON file

fix-something

Fix a random FIXME in the codebase (in the given scope, use "." for the whole codebase)

identify-doc-code-disagreements

Identify places in the $1 library where the docs and code disagree

identify-inconsistencies

Identify inconsistencies in the $1 library

identify-outdated-docstrings

Identify outdated docstrings in the $1 library

identify-style-issues

Identify divergences from the style guide in the $1 library

sync-tutorial-to-e2e-tests

Match tutorial script blocks to e2e pytest functions and add missing tests

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.

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.

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.

wait-for-agent

Wait for another agent to enter WAITING state, then execute follow-up instructions

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).

vet

Run vet immediately after ANY logical unit of code changes. Do not batch your changes, do not wait to be asked to run vet, make sure you are proactive.