Address Greptile PR review comments — read inline comments and summary, fix issues locally, push, reply to each thread, then tag Greptile to re-score and resolve threads.
End-to-end feature development loop. You describe a feature, iterate on the plan, then the team implements, reviews, ships a PR, and handles the configured PR-review bot autonomously. Notifies you at milestones. Use ONLY when the user wants the full autonomous implement→review→PR→verify loop for a multi-file feature. Do NOT use for: quick bug fixes, single-file edits, exploratory/discussion tasks, or anything the user wants to drive step-by-step.
Fetches and debugs a Langfuse trace OR session by ID or URL. A `.../sessions/<id>` URL renders a turn-by-turn conversation transcript (USER → TOOLS → ANNIE) across all the session's traces. A trace renders a span-tree overview with auto-suggested drill targets, then drills into a chosen section to surface system prompts, tool calls, and tool results. Renders both Anthropic block-style and langchain `tool_calls`-key messages, and strips noise (tool-call ids — incl. the giant gemini `__thought__` ids — plus `additional_kwargs`/`response_metadata`/message ids). Supports comparing two spans side-by-side. Use when the user provides a Langfuse trace/session ID or URL, mentions a langfuse.* link, or asks to debug, inspect, diagnose, or compare an LLM trace or conversation. Defaults to anyformat credentials (LANGFUSE_TRACING_*) and host (langfuse.anyformat.ai); other hosts work if LANGFUSE_HOST and LANGFUSE_PUBLIC_KEY/LANGFUSE_SECRET_KEY are set.
Query and debug anyformat's Datadog observability (logs, metrics, traces, monitors, incidents) via the plugin:datadog:mcp server, accounting for our non-standard loguru log structure. Use when searching or debugging anyformat logs/metrics/traces/monitors/incidents in Datadog, or when a Datadog log search for anyformat-core/backend returns 0 results.
Commit changes grouped by logical chunks, push to a feature branch, link a Linear ticket, and create a labelled PR. Targets 'dev' if it exists on origin (anyformat convention), otherwise the repo's default branch. Triggers on: commit, push, create PR, ship it, send PR.
Address failing CI checks on the current PR — group failures by root cause, fix locally, push, then watch the re-run. Pairs with react-to-greptile (comments) for full PR clean-up.
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
Find deepening opportunities in a codebase and propose refactors that turn shallow modules into deep ones. Aim is testability and AI-navigability. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable.