菜单
A specialist skill that analyses a codebase to understand its structure, dependencies, and architecture. This skill should be used at the start of a new project or when onboarding to an existing codebase.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | project-analysis |
| description | A specialist skill that analyses a codebase to understand its structure, dependencies, and architecture. This skill should be used at the start of a new project or when onboarding to an existing codebase. |
| allowed-tools | ["Read","Grep","Glob","Bash"] |
This skill should only use read-only commands and avoid modifying files.
Copy this checklist and use it to track your progress through the analysis process:
Project Analysis Checklist
- [ ] Gather a quick overview of the project by reading the README.md or equivalent documentation.
- [ ] Identify the main programming languages and frameworks used in the codebase.
- [ ] Map out the project structure, including key directories and files.
- [ ] Analyze dependencies by reviewing package management files (e.g., package.json, requirements.txt).
- [ ] Identify core modules and components of the application.
- [ ] Understand the data flow and architecture patterns used in the project.
- [ ] Review any existing tests to understand the testing strategy and coverage.
- [ ] Document any areas of the codebase that may require further investigation or clarification.
Here are some useful commands to help you analyze the codebase:
# List the main files and directories in the project
ls -R
# Check for package management files to identify dependencies
ls | grep -E 'package\.json|requirements\.txt|Pipfile|Gemfile'
# Display the contents of a package management file
cat package.json
cat requirements.txt
# Search for key architecture patterns or components
grep -r 'MVC\|Microservices\|Singleton\|Factory' .
# Identify test files and directories
find . -type f -name '*test*' -o -name '*spec*'
After completing the analysis, document your findings in a structured format. Include sections such as:
Design robust backend systems and APIs. Use when users ask to plan or implement services, data models, or integrations.
Create distinctive, production-grade frontend interfaces with high design quality. Use when users ask to build web components, pages, or applications.
A specialist skill that recognises and applies common software architecture patterns within a codebase. This skill should be used during the design and development phases of a project.
A skill that outlines best practices for using Git in a collaborative development environment, including branching strategies, commit conventions, and pull request workflows.
Analyses and optimises performance across frontend, backend and database interactions. Identifies bottlenecks and implements solutions to enhance speed and efficiency.
A specialist skill for security reviews, threat modeling, and remediation guidance. Use for auth/permissions changes, secrets or PII handling, public endpoints, or dependency upgrades.