autoresearch finalize

Engineering Community

Skill notes

Step 1 — Analyze and Propose Groups

Read autoresearch.jsonl. Filter to kept experiments only. Read autoresearch.md for context. Expand all short commit hashes to full hashes: git rev-parse <short_hash> Get the merge-base: git merge-base HEAD main For each kept commit, get the diff stat (use $BASE..<commit> for the first, <prev_kept>..<commit> for subsequent).

Step 2 — Write groups.json and Run

Write groups.json: Key rules: last_commit must be a full hash. Expand from jsonl short hashes with git rev-parse. No two groups may share a file. The script validates this and fails if violated. Then run:

Step 3 — Report

After the script finishes, report to the user: Branches created and what each contains Overall metric improvement (baseline → best) Show the cleanup commands from the script's summary output

Edge Cases

Only 1 kept experiment: One branch is fine — don't force splits. Overlapping files between groups: The script fails with an error naming the file. Merge the overlapping groups and retry. Non-experiment commits on the branch: Skip them — only process kept experiments from the jsonl.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@0-CYBERDYNE-SYSTEMS-0 · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1 — Analyze and Propose Groups

Read `autoresearch.jsonl`. Filter to kept experiments only. Read `autoresearch.md` for context. Expand all short commit hashes to full hashes: `git rev-parse <short_hash>` Get the merge-base: `git merge-base HEAD main` For each kept commit, get the diff stat (use `$BASE..<commit>` for the first, `<prev_kept>..<commit>` for subsequent).

02
Step 2 — Write groups.json and Run

Write `groups.json`: Key rules: `last_commit` must be a full hash. Expand from jsonl short hashes with `git rev-parse`. No two groups may share a file. The script validates this and fails if violated. Then run:

03
Step 3 — Report

After the script finishes, report to the user: Branches created and what each contains Overall metric improvement (baseline → best) Show the cleanup commands from the script's summary output

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.