Performs architectural review of files undergoing large-scale updates. Use proactively when refactoring, restructuring modules, or reviewing code organization. Provides actionable suggestions for renaming, moving functions, and restructuring modules.
Researches the backlog to find incomplete tasks, recently completed tasks, and suggests the most likely next task candidates based on dependencies, priorities, and completion patterns. Use when starting work sessions or deciding what to work on next.
Proposes a fix plan for a specific false positive issue group. Reads Ariadne core code to understand the detection gap and designs a concrete fix. Writes plan to a file.
Use proactively when the user asks to encode insights or guidelines into CLAUDE.md. Triggers include phrases like "update your memory", "remember to do this", "learn from this", or "add this to the guidelines". Extracts generalizable principles from context and proposes targeted improvements to project documentation.
Analyzes test coverage for a change set by reading source and test files, identifying which functions/modules have tests, and reporting coverage gaps. Use when reviewing PRs, before completing features, or when asked to check test coverage.
Investigates a single entry point candidate to determine if it is a true positive, dead code, or a false positive that Ariadne missed callers for. Returns a TriageEntryResult JSON.
Please investigate this task, debug it (using scripts in /tmp if needed) in order to find the root cause of the issue. Find the and suggest the best strategies for fixing the issue.
Runs before the agent uses a tool for Write and Edit tool calls, executing file_naming_validator.ts and backlog_validator.ts (2 commands). From CRJFisher/ariadne.
Runs when the agent finishes a response, executing build_stop.ts, eslint_stop.ts, file_naming_validator_stop.ts, test_file_enforcement_stop.ts, run_tests_stop.ts and entrypoint_stop.ts (6 commands). From CRJFisher/ariadne.
Run live tests of the Ariadne MCP server using Claude Code in headless mode. Tests tool discovery, invocation, and filtering. Use when validating MCP server changes or checking integration with Claude Code.
Runs the full entry point self-repair pipeline. Detects entry points in Ariadne packages or external codebases, triages false positives via sub-agents, plans fixes for each issue group with competing proposals and multi-angle review, and creates backlog tasks.