repo-intake-and-plan

作成者: lllllllama

Rigor Intake helper for README-first deep learning repo reproduction. Use when the task is specifically to scan a repository, read the README and common project files, extract documented commands, classify inference, evaluation, and training candidates, and return the smallest trustworthy reproduction plan to the main orchestrator. Do not use for environment setup, asset download, command execution, final reporting, paper lookup, or end-to-end orchestration.

npx skills add https://github.com/lllllllama/rigorpilot-skills --skill repo-intake-and-plan

repo-intake-and-plan

Use this as the Rigor Intake helper. The installed slug remains repo-intake-and-plan for compatibility.

When to apply

  • At the beginning of README-first reproduction work.
  • When the main skill needs a fast map of repo structure and documented commands.
  • When inference, evaluation, and training candidates must be classified conservatively.
  • When the user explicitly wants to inspect the repo first and not run anything yet.

When not to apply

  • When execution has already started and the task is now about running commands or writing outputs.
  • When the target is not a repository-backed reproduction task.
  • When the user only wants paper interpretation without repo inspection.
  • When the user already has a selected documented command and only needs setup or execution.

Clear boundaries

  • This skill scans and plans.
  • This skill is helper-tier and should usually be orchestrator-invoked.
  • It does not install environments.
  • It does not prepare large assets.
  • It does not execute substantive reproduction commands.
  • It does not decide high-risk patching.

Input expectations

  • Target repository path.
  • Access to README and common project files if present.
  • Optional user hints about desired priority, such as inference-first.

Output expectations

  • concise repo structure summary
  • documented command inventory
  • inferred candidate categories: inference, evaluation, training, other
  • minimum trustworthy reproduction recommendation
  • notable ambiguity or risk list

Notes

Use references/repo-scan-rules.md and helper scripts under scripts/.

lllllllamaのその他のスキル

ai-research-explore
lllllllama
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
lllllllama
Rigor Analyze / Rigor Auditの読み取り専用スキル。深層学習研究リポジトリ向け。ユーザーがリポジトリを読み解き、モデル構造や学習・推論のエントリポイントを調査し、設定や挿入箇所を確認し、コードを変更したり重いジョブを実行せずに不審な実装パターンを指摘したい場合に使用する。アクティブなコマンド実行、大規模なリファクタリング、推測的なコード適応、自動バグ修正には使用しない。
developmentcode-reviewresearch
ai-research-reproduction
lllllllama
RigorPilotの再現モードオーケストレーター。READMEファーストの深層学習リポジトリ再現用。ユーザーがエンドツーエンドで最小限の信頼性のあるフローを求める場合に使用。リポジトリを最初に読み、最小の文書化された推論または評価ターゲットを選択し、取り込み、セットアップ、信頼できる実行、オプションの信頼できるトレーニング、オプションのリポジトリ分析、オプションの論文ギャップ解決を調整し、保守的なパッチルールを適用し、証拠の前提の逸脱と人間の判断ポイントを記録する。
researchdevelopmentdocument
explore-code
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...
developmentresearchcode-review
minimal-run-and-audit
lllllllama
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
lllllllama
README優先の深層学習リポジトリ再現のためのRigor Setupスキル。READMEにドキュメント化されたリポジトリで実行前に、保守的なconda優先環境、チェックポイントとデータセットのパス前提、キャッシュ場所のヒント、セットアップノートを準備するタスクに使用する。リポジトリスキャン、完全なオーケストレーション、論文解釈、最終実行レポート、特定の再現対象に紐づかない汎用的な環境セットアップには使用しない。
developmentdevops
explore-run
lllllllama
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
safe-debug
lllllllama
ディープラーニング研究作業のためのRigor Debug / Rigor Auditスキル。ユーザーがトレースバック、ターミナルエラー、CUDA OOM、チェックポイント読み込み失敗、形状不一致、NaN損失症状、またはトレーニング失敗を貼り付け、パッチ適用前に保守的な診断を希望し、デバッグ修正が研究貢献と明確に分離されている場合に使用します。広範なリファクタリング、推測的な適応、自動探索的パッチ適用、または一般的なリポジトリの習熟には使用しないでください。
developmenttestingcode-review