analyze-project
This skill performs read-only analysis and auditing of deep learning research repositories. It helps users understand model structures, training/inference entry points, and configuration relationships, identifying potential insertion points or suspicious implementation patterns. This provides deep project insights without modifying code or running heavy tasks.
npx skills add https://github.com/lllllllama/rigorpilot-skills --skill analyze-projectBefore / After Comparison
1 组Before this skill, developers manually sifted through extensive codebases, configurations, and documentation to grasp a deep learning project's structure, models, and training pipelines. This was time-consuming and often led to missed critical information, slowing project onboarding or introducing potential errors.
This skill rapidly performs read-only analysis of deep learning research repositories, automatically identifying model structures, training/inference entry points, and configuration relationships, while flagging suspicious patterns. This significantly reduces project comprehension time, boosting development efficiency and code 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.mdanalysis_outputs/RISKS.mdanalysis_outputs/status.json
Notes
Use references/analysis-policy.md and the shared references/research-pitfall-checklist.md.
User Reviews (0)
Write a Review
No reviews yet
Statistics
User Rating
Rate this Skill