autoresearch
CommandAutonomous iteration loop: modify, verify, keep/discard against any metric
Crush errors one-by-one until zero remain: tests, types, lint, build
> /plugin marketplace add uditgoenka/autoresearch> /plugin install autoresearch@autoresearch
name: autoresearch:fix description: "Crush errors one-by-one until zero remain: tests, types, lint, build" argument-hint: "[Target: <cmd>] [Scope: <glob>] [Guard: <cmd>] [Iterations: N] [--evals] [--from-debug]" disable-model-invocation: true
EXECUTE IMMEDIATELY.
Extract from $ARGUMENTS:
If Target and Scope both missing: 1. Auto-detect failures: run test suite, type checker, linter, build 2. Present results via AskUserQuestion (single batched call): Q1 (Fix What): "Found [N] test failures, [M] type errors, [K] lint errors. Fix what?" — everything, only tests, only types, only lint Q2 (Guard): "Safety command that must always pass?" — npm test, tsc, npm run build, skip Q3 (Scope): "Which files can I modify?" — suggested globs from error locations + all Q4 (Launch): "Ready?" — fix until zero, fix with limit, cancel If all provided → skip setup. If --from-debug → read handoff.json for scope and findings.
Verify: git repo exists, clean working tree, no lock files, no detached HEAD. Fail fast on critical issues.
1. Run Target command → count errors (metric = error count, direction = lower_is_better) 2. Record baseline in TSV 3. Create output directory: `autoresearch/fix-{YYMMDD}-{HHMM}/` 4. TSV header: `# metric_direction: lower_is_better\niteration\ttimestamp\terror_type\terror_fixed\tcommit\tmetric\tdelta\tguard\tstatus\tdescription`
Order: crash/fatal → test failures → type errors → lint → warnings. Within category: easiest first (single-file fixes before cross-file).
Append row: iteration, timestamp, error_type, error_fixed, commit/-, metric (error count), delta, guard, status, description
If --evals: check if current_iteration % interval == 0 → run checkpoint analysis.
If bounded: current_iteration >= max_iterations → exit loop, print summary.
Print: total errors fixed, remaining errors, error types distribution, fix success rate.
If --evals present:
After completion, write handoff.json to output directory: version "2.1.0", source "fix", timestamp, status (COMPLETE|USER_INTERRUPT|BOUNDED|ERROR), results_tsv path, findings = unfixed errors, config{target, scope, guard}. Invoke next target in --chain order via the `autoresearch` skill's Subcommand routing. Propagate --evals flag.
Turn Claude Code, OpenCode, or OpenAI Codex into a relentless improvement engine. Based on Karpathy's autoresearch — constraint + mechanical metric + autonomous iteration = compounding gains.
Autonomous iteration loop: modify, verify, keep/discard against any metric
Hunt bugs with scientific method: hypothesize, test, falsify, repeat
Analyze iteration results: trends, plateaus, regressions, recommendations
Research ICP challenges, discover improvements, generate PRDs
Scout codebase and auto-generate docs — or a navigable wiki knowledge base — with validation-fix loop
Convert a goal into validated Scope, Metric, Direction, Verify config
One-time setup after installing ARIS as a Claude Code plugin — registers the Codex reviewer MCP server from the plugin directory…
name: sc:agent description: SC Agent — session controller that orchestrates investigation, implementation, and review category:…