git:20260822.b84be12 to git:20260822.79ec489

2 added, 2 removed. Audit A to A.

---

name: analyze-project

description: Rigor Analyze / Rigor Audit 只读技能，用于深度学习研究仓库的深入分析。当用户想阅读并理解仓库、检查模型结构与训练/推理入口、审阅配置与插入点，或在不动代码、不跑重任务的前提下标记可疑实现模式时使用。不适用于主动执行命令、大规模重构、推测性代码适配或自动修 bug。

en_description: 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.

zh_displayName: 项目分析

- category: 开发框架与平台

- en_category: Dev Frameworks & Platforms

+ category: 工程实践与质量

+ en_category: Engineering Practice & Quality

---

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