Conversation
| @@ -0,0 +1,68 @@ | |||
| # Domain Map Template | |||
There was a problem hiding this comment.
You basically add this skill and then remove it. You would need to add a generate-explore.md prompt for it to be run with the following. I wonder if there's a better way to do this...
---
description: Analyzes this codebase and generates a customized /explore skill in .agents/explore/
---
[generate-explore skill](.agents/generate-explore/SKILL.md)Then you need to add the explore.md prompt so you can call /explore in vscode
---
description: Architecture guide for C12 Core. Use when asked about architecture, how code is structured, or when tracing code through the stack.
---
[explore skill](.agents/explore/SKILL.md)
There was a problem hiding this comment.
Pull request overview
Adds a new generate-explore skill that can analyze an arbitrary repository and generate a customized .agents/explore/ skill (plus reference docs) to help developers understand architecture, drill into topics/paths, and trace code backwards.
Changes:
- Introduces
skills/generate-explore/SKILL.mddefining the multi-phase “analyze → generate → validate → report” workflow. - Adds three reference templates (SKILL, domain discovery map, trace playbook) that the generator fills in to produce the
.agents/explore/output.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| skills/generate-explore/SKILL.md | New generator skill that discovers stack/structure and outputs a tailored /explore skill + references. |
| skills/generate-explore/references/SKILL_TEMPLATE.md | Template for the generated .agents/explore/SKILL.md (3 modes + follow-up). |
| skills/generate-explore/references/DOMAIN_MAP_TEMPLATE.md | Template for discovery conventions and a “Domain Profile” output format. |
| skills/generate-explore/references/TRACE_PLAYBOOK_TEMPLATE.md | Template for the trace-backwards algorithm and stack-diagram output format. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| Present the trace as a vertical stack: | ||
|
|
||
| ``` | ||
| {{STACK_DIAGRAM_FORMAT}} | ||
| ``` |
There was a problem hiding this comment.
The template wraps the entire generated file in a markdown fenced block, but later uses triple-backtick fences again for the stack diagram. In Markdown, that inner will terminate the outer fence early, so the template won’t render/copy correctly. Use a different outer fence delimiter (e.g., 4 backticks) or switch the inner diagram fence to tildes/indented code so nested fences don’t conflict.
| ``` | ||
| {{STACK_DIAGRAM_FORMAT}} | ||
| ``` |
There was a problem hiding this comment.
This template encloses the generated playbook in a ```markdown code fence, but the stack-diagram example uses triple backticks inside it. That closes the outer fence, breaking the template structure and copy/paste instructions. Use a different outer fence delimiter (e.g., 4 backticks) or change the inner example to a non-conflicting fence (tildes/indented code).
| ``` | |
| {{STACK_DIAGRAM_FORMAT}} | |
| ``` | |
| ~~~ | |
| {{STACK_DIAGRAM_FORMAT}} | |
| ~~~ |
| ``` | ||
| ## <Concept> Domain Profile | ||
|
|
||
| {{PROFILE_SECTIONS}} | ||
| ``` |
There was a problem hiding this comment.
The template is wrapped in a markdown fenced block, but the Domain Profile section includes an inner triple-backtick fence. That inner will end the outer fence, so the rendered template and the intended generated output won’t match. Use a different outer fence delimiter (e.g., 4 backticks) or change the inner example fence to tildes/indented code.
| ``` | |
| ## <Concept> Domain Profile | |
| {{PROFILE_SECTIONS}} | |
| ``` | |
| ~~~ | |
| ## <Concept> Domain Profile | |
| {{PROFILE_SECTIONS}} | |
| ~~~ |
This skill is used to generate the
/explorecommand to assess a codebase and help a developer understand how parts of it work. Could be useful for a new developer joining a project or assessing/learning an inherited brownfield application.