autoresearch-finalize — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited autoresearch-finalize (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Turn a noisy autoresearch branch into clean, independent branches — one per logical change, each starting from the merge-base.
autoresearch.jsonl. Filter to kept experiments only.autoresearch.md for context.git rev-parse <short_hash>git merge-base HEAD mainapi.js and group 2 calls it in parser.js, group 2's branch won't work in isolation. Flag dependencies.Present the proposed grouping:
Proposed branches (each from merge-base, independent):
1. **<description>** (commits abc1234, def5678)
Files: file1.py, file2.py
Metric: 42.3 → 38.1 (-9.9%)
2. **<description>** (commits ghi9012)
Files: config.json
Metric: 38.1 → 31.7 (-16.8%)Wait for approval before proceeding.
For each approved group:
BASE=$(git merge-base HEAD main)
git checkout -b autoresearch/final/<group-name> $BASE
git cherry-pick <commit1> <commit2> ...If cherry-pick conflicts, resolve by taking the experiment's version (the whole point is to preserve the improvement).
For each branch:
Finalized branches:
1. autoresearch/final/<name> — <metric improvement>, ready to merge
2. autoresearch/final/<name> — <metric improvement>, depends on branch 1The user can now review and merge each branch independently (or together if there are dependencies).
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.