---
id: gh-analyze-project
name: "analyze-project"
url: https://skills.yangsir.net/skill/gh-analyze-project
author: lllllllama
domain: data-ai
tags: ["deep-learning", "code-analysis", "repository-audit", "model-understanding", "static-inspection"]
install_count: 330700
rating: 4.90 (120 reviews)
github: https://github.com/lllllllama/rigorpilot-skills/tree/main/skills/analyze-project
---

# analyze-project

> 此技能用于对深度学习研究仓库进行只读分析和审计。它能帮助用户理解模型结构、训练/推理入口、配置关系，并识别潜在的插入点或可疑实现模式，从而在不修改代码或执行繁重任务的情况下，深入洞察项目。

**Stats**: 330,700 installs · 4.9/5 (120 reviews)

## Before / After 对比

### 深度学习项目理解效率

**Before**:

在没有此技能之前，开发者需要手动阅读大量代码、配置文件和文档，才能理解一个深度学习项目的结构、模型和训练流程。这通常耗时且容易遗漏关键信息，导致项目启动缓慢或引入潜在错误。

**After**:

此技能能够快速对深度学习研究仓库进行只读分析，自动识别模型结构、训练/推理入口和配置关系，并标记可疑模式。这大大缩短了项目理解时间，提高了开发效率和代码质量。

| Metric | Before | After | Change |
|---|---|---|---|
| 项目理解时间 | 8小时 | 1小时 | -88% |

## Readme

# 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`.


---
*Source: https://skills.yangsir.net/skill/gh-analyze-project*
*Markdown mirror: https://skills.yangsir.net/api/skill/gh-analyze-project/markdown*