一键导入
context-map
Generate a map of all files relevant to a task before making changes
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Generate a map of all files relevant to a task before making changes
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | context-map |
| description | Generate a map of all files relevant to a task before making changes |
Before implementing any changes, analyze the codebase and create a context map.
{{task_description}}
## Context Map
### Files to Modify
| File | Purpose | Changes Needed |
| ------------ | ----------- | -------------- |
| path/to/file | description | what changes |
### Dependencies (may need updates)
| File | Relationship |
| ----------- | ---------------------------- |
| path/to/dep | imports X from modified file |
### Test Files
| Test | Coverage |
| ------------ | ---------------------------- |
| path/to/test | tests affected functionality |
### Reference Patterns
| File | Pattern |
| --------------- | ----------------- |
| path/to/similar | example to follow |
### Risk Assessment
- [ ] Breaking changes to public API
- [ ] Database migrations needed
- [ ] Configuration changes required
Do not proceed with implementation until this map is reviewed.
Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.
Audit and auto-fix consistency, performance, and style issues across the wiki codebase. Use when reviewing code quality, preparing releases, onboarding contributors, or after bulk changes to TypeScript components, MDX docs, CSS, or imports.
Prompt and workflow for generating conventional commit messages using a structured XML format. Guides users to create standardized, descriptive commit messages in line with the Conventional Commits specification, including instructions, examples, and validation.
Pre-merge QA checklist for documentation changes. Use when reviewing a PR, preparing a release, or validating docs quality. Checks links, headings, category metadata, build output, and translation readiness.
Apply consistent visual design when creating or reviewing UI components. Covers design tokens, component patterns, glass-morphism cards, responsive grids, and accessibility. Use when building new homepage sections, auditing visual consistency, or reviewing CSS changes.
Create an llms.txt file from scratch based on repository structure following the llms.txt specification at https://llmstxt.org/