* Add copilot-spaces skill for loading project-specific context
New skill that teaches agents to use Copilot Spaces MCP tools
(list_copilot_spaces, get_copilot_space) to discover and load
curated project context into conversations. Covers discovery
workflow, loading spaces by owner/name, and using space content
to ground responses in team-specific docs, code, and standards.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Improve copilot-spaces skill with real-world usage patterns
- Add 'Spaces as workflow engines' pattern for multi-step processes
- Add 'Follow the breadcrumbs' step for fetching referenced resources
- Document read-only API limitation (no create/update/delete)
- Add filtering tip for list_copilot_spaces by owner
- Add large output handling guidance (20KB+ spaces)
- Add Example 4: Space as a workflow engine
- Strengthen tips with actionable guidance
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add Spaces CRUD REST API to copilot-spaces skill
- Document full CRUD API endpoints (create, update, delete, collaborators)
- Add 'Managing Spaces' workflow section with gh api examples
- Add Example 5: updating Space instructions programmatically
- Fix incorrect 'read-only' claim - MCP is read-only, REST API is full CRUD
- Add scope requirements (user scope for writes)
- Add resource management tips (array replacement, _destroy)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add issue fields, issue types, and list_issue_types to github-issues skill
- Add list_issue_types to available MCP tools table
- Add type parameter to optional parameters with guidance
- Expand issue types section: MCP tools (preferred) + GraphQL (advanced)
- Document org-level type discovery, create/update with type, GraphQL mutations
- Add issue fields section: discover, read, set via GraphQL
- Note required GraphQL-Features headers (issue_fields, issue_types)
- Update skill description to mention fields, types, dates, priority
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add Projects V2 guidance to github-issues skill
Include MCP tools (projects_list, projects_get, projects_write) and
GraphQL examples for project item management.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add sub-issues section, move issue fields to end with preview note
- Add Sub-Issues and Parent Issues section (MCP, REST, GraphQL)
- Add issue_read tool to MCP tools table
- Move Issue Fields to last section with private preview callout
- Link to community discussion for requesting access
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Prefer issue types over labels for categorization
Update guidance and examples to use type parameter (Bug, Feature)
instead of equivalent labels when issue types are available.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Prefer issue fields over project fields for metadata
Issue fields live on the issue and travel across projects.
Project fields are scoped to a single project.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add issue dependencies (blocked by/blocking) section
Covers REST endpoints (list, add, remove) and GraphQL
(blockedBy, blocking, issueDependenciesSummary, mutations).
Also documents tracked issues read-only fields.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add project discovery workflow for progress reports
Teach agents how to find projects by name, discover fields
and iterations, paginate items, and build status breakdowns.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Generate updated skill listing after SKILL.md changes
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Split skill into reference files per reviewer feedback
Move sub-issues, dependencies, issue types, projects, and issue fields
into separate references/ files. Main SKILL.md now contains core MCP
workflow and a capability table pointing to each reference. This way
the agent only loads the knowledge it needs for the specific task.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Tadas LabudisandCopilot