원클릭으로
what-context-needed
Ask Copilot what files it needs to see before answering a question
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Ask Copilot what files it needs to see before answering a question
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
Generate a map of all files relevant to a task before making changes
| name | what-context-needed |
| description | Ask Copilot what files it needs to see before answering a question |
Before answering my question, tell me what files you need to see.
{{question}}
## Files I Need
### Must See (required for accurate answer)
- `path/to/file.ts` — [why needed]
### Should See (helpful for complete answer)
- `path/to/file.ts` — [why helpful]
### Already Have
- `path/to/file.ts` — [from earlier in conversation]
### Uncertainties
- [What I'm not sure about without seeing the code]
After I provide these files, I'll ask my question again.