Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
lllllllama avatar

Explore Code

  • 176k installs
  • 512 repo stars
  • Updated July 26, 2026
  • lllllllama/rigorpilot-skills

explore-code is a Claude Code skill for bounded, auditable exploratory code modifications in deep learning research on isolated branches.

About

A code-level exploration skill for deep learning research. Use it when you want to make targeted code changes like adding adapters, replacing heads, or transplanting modules while maintaining isolation and audit trails.

  • Implements bounded exploratory code changes on isolated branches
  • Transplants modules, adapts backbones, inserts LoRA/adapter layers
  • Records rollback-aware changesets and scientific justification

Explore Code by the numbers

  • 175,993 all-time installs (skills.sh)
  • +25,326 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #10 of 16,659 AI & Agent Building skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

explore-code capabilities & compatibility

Capabilities
code adaptation · module transplant · audit trail recording · rollback planning
Use cases
code review · refactoring · research
npx skills add https://github.com/lllllllama/rigorpilot-skills --skill explore-code

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs176k
repo stars512
Security audit1 / 3 scanners passed
Last updatedJuly 26, 2026
Repositorylllllllama/rigorpilot-skills

What it does

Implement auditable candidate code changes for deep learning research with rollback-aware records.

Who is it for?

Module transplants,Backbone adaptation,LoRA/adapter insertion,Low-risk module combination

Skip if: Trusted baseline work,Conservative debugging,Broad refactoring,Default repository analysis

When should I use this skill?

The researcher explicitly authorizes exploratory code changes on an isolated branch to adapt a backbone, insert adapters, or stitch together low-risk ideas.

What you get

CHANGESET.md, SCIENTIFIC_CHANGELOG.md, COMPARABILITY_REPORT.md documenting what changed, why it's meaningful, and rollback instructions.

  • explore_outputs/CHANGESET.md
  • explore_outputs/SCIENTIFIC_CHANGELOG.md
  • explore_outputs/COMPARABILITY_REPORT.md

By the numbers

  • Outputs 4 structured documents in explore_outputs/ with changesets and justification

Files

SKILL.mdMarkdownGitHub ↗

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.

Related skills

Forks & variants (3)

Explore Code has 3 known copies in the catalog totaling 455 installs. They canonicalize to this original listing.

How it compares

Choose explore-code for authorized isolated code edits; choose ai-research-explore when coordinating hypothesis runs on current_research rather than branch-local implementation.

FAQ

Is work kept isolated?

Yes. Changes stay on an isolated branch or worktree, never modifying the trusted baseline.

What counts as low-risk?

Source-anchored copying, minimal adaptation, module replacement with same interface signatures.

Is Explore Code safe to install?

skills.sh reports 1 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

AI & Agent Buildingresearchagentsautomation

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.