autoresearch

Run an autonomous loop that modifies code, measures metrics, and keeps or reverts changes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/shuretokki/void --skill autoresearch-shuretokki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autoresearch
Source: https://github.com/shuretokki/void/tree/main/.agents/skills/autoresearch
Command: npx skills add https://github.com/shuretokki/void --skill autoresearch-shuretokki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Autoresearch removes the manual grind of incremental performance or behavior tuning by running an autonomous loop that proposes changes, commits them, runs a user-defined metric command, measures results, and keeps or reverts changes based on objective outcomes. It ensures every experiment is measured, tracked, and reversible so humans don't have to manually try and evaluate many small modifications.

Core Features & Use Cases

  • Interactive Setup: Guides the user to define a clear goal, the exact metric command and extraction method, in-scope/out-of-scope files, constraints, and experiment budget before any changes are made.
  • Autonomous Experiment Loop: Creates a branch, commits each experiment, runs the metric command, extracts the metric, and either keeps or reverts the commit while logging results in results.tsv.
  • Safety and Reproducibility: Uses git-based commits and reverts, avoids modifying out-of-scope files, and requires user approval for environment or dependency changes.
  • Use Case Examples: Optimize benchmark timings, reduce memory usage, increase test pass rates, or minimize bundle size in codebases where a reproducible command yields a numeric metric.

Quick Start

Start an autonomous optimization run by telling the agent your goal, providing the exact metric command and extraction rule, listing which files are in-scope, and confirming the setup.

Frequently Asked Questions about autoresearch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate iterative code optimization and benchmarking?

Automate iterative code optimization by running an autonomous experimentation loop that modifies code, executes a reproducible metric command, and keeps or reverts changes based on measured outcomes. It uses git commits to ensure every modification is tracked and reversible.

How does autonomous experimentation handle reverting failed code changes?

Autonomous experimentation handles reverting failed changes by using git-based commits and reverts. After running the metric command, if the numeric outcome does not improve, the loop automatically reverts the commit while logging the results.

Can I use autonomous experimentation to increase test pass rates in a git repository?

Yes, you can use autonomous experimentation to increase test pass rates in a git repository. It applies to programming projects where improvements are quantified by reproducible commands, such as test pass counts or benchmark timings.

What do I need to set up before starting an autonomous experimentation loop?

Before starting an autonomous experimentation loop, you need a git repository with terminal access, a concrete metric command with an extraction method, and explicit definitions of in-scope and out-of-scope files. The interactive setup guides you through defining these constraints and the experiment budget.

What are the limitations of using an autonomous loop for performance tuning?

Limitations include requiring a reproducible metric command that yields a numeric outcome and repeated run capability. The loop avoids modifying out-of-scope files and requires explicit user approval for any environment or dependency changes during the experimentation process.

What is the best way to reduce memory usage through autonomous code modifications?

The best way to reduce memory usage is running an autonomous experimentation loop that proposes code modifications, measures the resource output, and keeps the commit only if it improves the metric. Results are tracked in a log for objective evaluation.