autoresearch
Autoresearch
Autonomous experiment loop: try ideas, measure results, keep what works, discard what doesn't, never stop.
Works for any optimization target: test speed, bundle size, LLM training, build times, Lighthouse scores, binary size, latency, memory usage.
Setup
If autoresearch.md already exists in the working directory, skip setup and resume the loop — read autoresearch.md, autoresearch.jsonl, and git log, then continue experimenting.
Otherwise:
- Gather context: Ask (or infer from
$ARGUMENTSand conversation) the Goal, Command to benchmark, Primary metric (name + direction), Files in scope, and Constraints. - Create branch:
git checkout -b autoresearch/<goal>-<date>(e.g.autoresearch/test-speed-2026-03-21). - Read source files: Understand the workload deeply before writing anything. Read every file in scope.
- Write session files: Create
autoresearch.mdandautoresearch.sh(see templates below). If constraints require correctness validation (tests must pass, types must check), also createautoresearch.checks.sh. Commit all. - Run baseline: Execute the first experiment with no changes to establish the baseline metric.
- Start looping: Begin the experiment loop immediately after the baseline is logged.
More from paulrberg/dot-agents
bump-release
This skill should be used when the user asks to "bump release", "cut a release", "tag a release", "bump version", "create a new release", or mentions release versioning, changelog updates, or version tagging workflows.
11yeet
This skill should be used when the user asks to "create a pull request", "create PR", "open PR", "update a pull request", "update PR", "create an issue", "file an issue", "create a GitHub issue", "create a Claude Code issue", "report a bug in Claude Code", "create a Codex issue", "report a bug in Codex CLI", "create a Sablier issue", "file an issue in sablier-labs", "create a discussion", "start a GitHub discussion", "yeet a PR", "yeet an issue", "yeet a discussion", or mentions GitHub contribution workflows.
11code-simplify
This skill should be used when the user asks to "simplify code", "clean up code", "refactor for clarity", "reduce complexity", "improve readability", "make this easier to maintain", or asks to simplify recently modified code.
10vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with
9cli-just
This skill should be used when the user asks to "create a justfile", "write just recipes", "configure just settings", "add just modules", "use just attributes", "set up task automation", mentions justfile, just command runner, or task automation with just.
9work
This skill should be run only when the user explicitly invokes it. Orchestrates end-to-end task implementation — understands the task, assesses complexity, implements directly or via a team of subagents for complex work, and always finishes with a code-polish pass.
9