‹ 首页

analyze-project

@lllllllama · 收录于 2 周前 · 上游提交 2 天前

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.

场景深度学习代码审查仓库结构分析

适合你，如果你需要深入检查深度学习项目的代码质量与潜在问题

/ 下载安装
https://github.com/lllllllama/rigorpilot-skills/tree/main/skills/analyze-project ↗
/ 通过 npx 安装 校验哈希
npx oh-my-skill add lllllllama/rigorpilot-skills/analyze-project
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- lllllllama/rigorpilot-skills/analyze-project
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify lllllllama/rigorpilot-skills/analyze-project
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
–GitHub stars
~394最小装载
~483含声明引用
~5.2K文本包总量
索引托管

怎么用

商店整理自技能原文 · 版本 3ab5052 · 表述以原文为准
它做什么

装上后，Claude 会以只读方式分析深度学习研究仓库，输出仓库摘要（SUMMARY.md）、风险提示（RISKS.md）和状态文件（status.json），不会修改代码或运行繁重任务。

什么时候触发

当用户想在修改前理解一个深度学习仓库，或需要查看模型结构、训练入口、配置关系，或要求只读分析时触发。

装好后可以这样说
Claude 会生成仓库摘要和结构图。
Claude 会输出风险提示文件。
技能原文 SKILL.md作者撰写 · MIT · 3ab5052

analyze-project

Use this as the Rigor Analyze / Rigor Audit read-only skill. The installed slug remains analyze-project for compatibility.

Use the shared operating principles in ../../references/agent-operating-principles.md; this skill should guide read-only analysis without constraining the model's project-specific reasoning.

When to apply
  • The user wants to understand a deep learning repository before changing it.
  • The user needs a map of model structure, training entrypoints, inference entrypoints, and config relationships.
  • The user wants conservative suggestions about likely insertion points or suspicious implementation patterns.
  • The user explicitly wants read-only analysis and not heavy execution.
When not to apply
  • When the main task is to execute a failing command or debug a traceback.
  • When the user wants environment setup or asset download only.
  • When the user wants speculative adaptation or broad exploratory patching.
  • When the task is a general literature summary without repository analysis.
Clear boundaries
  • This skill is read-mostly.
  • It may run lightweight static inspection helpers.
  • It does not patch repository code.
  • It does not own final reproduction outputs.
  • It should mark suspicious patterns as heuristics, not confirmed bugs.
Output expectations
  • analysis_outputs/SUMMARY.md
  • analysis_outputs/RISKS.md
  • analysis_outputs/status.json
Notes

Use references/analysis-policy.md and the shared ../../references/research-pitfall-checklist.md.

按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。
…