Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.
Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.
Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
Compact, emoji-tagged quick-scan summary of Claude's own most recent long response in this conversation — actions taken, things to watch out for, decisions needed, files produced, suggested next steps. This is a dedicated minimal-invocation command: ALWAYS trigger it when the user's message is just the word…
Use when the user wants to add, remove, prune, or evaluate RSS/Atom feeds for a web-mcp instance — e.g. "add some good AI news feeds", "check if any of my feeds are dead", "this feed is too noisy, replace it".
Use when the user wants a synthesized summary or research digest built from indexed feeds — e.g. "what's happening in AI this week", "summarize the news on X", "give me a digest of the last 24 hours".