explore-code

bởi lllllllama

Rigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated branch or worktree to transplant modules, adapt a backbone, add LoRA or adapter layers, replace a head, or stitch together meaningful low-risk migration ideas with rollback-aware records in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted...

npx skills add https://github.com/lllllllama/rigorpilot-skills --skill explore-code

Tải ZIP GitHub

explore-code

Use this as the Rigor Improve implementation leaf skill. The installed slug remains explore-code for compatibility.

Use the shared operating principles in ../../references/agent-operating-principles.md; this skill should guide bounded candidate code work without over-prescribing implementation details.

When to apply

When the researcher explicitly authorizes exploratory code changes on an isolated branch or worktree.
When the task is source-anchored module transplant, backbone adaptation, LoRA or adapter insertion, or low-risk module combination.
When summary-level recording is sufficient and the result is a candidate, not a trusted conclusion.

When not to apply

When the request is for trusted baseline work, conservative debugging, or normal training execution.
When the user did not explicitly authorize exploratory modifications.
When the task is a broad refactor or a from-scratch idea implementation.

Clear boundaries

This skill owns exploratory code modifications only.
It must keep work isolated from the trusted baseline.
Use ai-research-explore instead when the task spans both current_research coordination and exploratory runs.
It may hand off execution to minimal-run-and-audit or run-train.
It should favor source-anchored copying and minimal adaptation over freeform rewrites.
It should record why a candidate change is meaningful, how to roll it back, and why it remains a candidate rather than a verified contribution.

Output expectations

explore_outputs/CHANGESET.md
explore_outputs/SCIENTIFIC_CHANGELOG.md
explore_outputs/COMPARABILITY_REPORT.md
explore_outputs/TOP_RUNS.md
explore_outputs/status.json

Notes

Use references/explore-policy.md, ../../references/research-rigor-principles.md, scripts/plan_code_changes.py, and scripts/write_outputs.py.

Thêm skills từ lllllllama

ai-research-explore

Rigor Explore compatible skill slug for meaningful and potentially novel deep learning research candidates. Use when the researcher has chosen the task family, dataset, benchmark, evaluation method, provided SOTA references, and wants candidate-only exploration on top of `current_research` with auditable repo understanding, idea gating, fair comparison, and governed experiments written to `explore_outputs/`. Do not use for README-first trusted reproduction, open-ended direction finding,...

researchdata-analysisapi

analyze-project

Rigor Analyze / Rigor Audit read-only skill for deep learning research repositories. Use when the user wants to read and understand a repository, inspect model structure and training or inference entrypoints, review configs and insertion points, or flag suspicious implementation patterns without modifying code or running heavy jobs. Do not use for active command execution, broad refactoring, speculative code adaptation, or automatic bug fixing.

developmentcode-reviewresearch

ai-research-reproduction

RigorPilot reproduce-mode orchestrator for README-first deep learning repository reproduction. Use when the user wants an end-to-end, minimal-trustworthy flow that reads the repository first, selects the smallest documented inference or evaluation target, coordinates intake, setup, trusted execution, optional trusted training, optional repository analysis, and optional paper-gap resolution, enforces conservative patch rules, records evidence assumptions deviations and human decision points,...

researchdevelopmentdocument

minimal-run-and-audit

Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized `repro_outputs/` files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.

developmenttestingcode-review

env-and-assets-bootstrap

Rigor Setup skill for README-first deep learning repo reproduction. Use when the task is specifically to prepare a conservative conda-first environment, checkpoint and dataset path assumptions, cache location hints, and setup notes before any run on a README-documented repository. Do not use for repo scanning, full orchestration, paper interpretation, final run reporting, or generic environment setup that is not tied to a specific reproduction target.

developmentdevops

Rigor Improve / Rigor Explore run leaf skill for bounded exploratory evidence in deep learning research repositories. Use when the researcher explicitly authorizes exploratory runs such as small-subset validation, short-cycle guess-and-check, batch sweeps, idle-GPU search, or quick transfer-learning trials, with fair-comparison caveats and no-overclaim summaries in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline...

researchdevelopmentdata-analysis

Rigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training failure and wants conservative diagnosis before any patching, with debug fixes clearly separated from research contributions. Do not use for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization.

developmenttestingcode-review

paper-context-resolver

Rigor Paper Context helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow reproduction-critical gap and the task is to resolve a specific paper detail such as dataset split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumption from primary paper sources while recording conflicts. Do not use for general paper summary, repo scanning, environment setup, command execution, title-only paper lookup, or...

researchdocumentdata-analysis