You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 2e1042e
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: .github/copilot-instructions.md
+13-6Lines changed: 13 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -189,12 +189,19 @@ All workflows run on push/PR unless noted. Located in `.github/workflows/`:
189
189
190
190
1. Add tool implementation in `pkg/github/` (e.g., `foo_tools.go`)
191
191
2. Register tool in appropriate toolset in `pkg/github/` or `pkg/toolsets/`
192
-
3. Write unit tests following the tool test pattern
193
-
4. Run `UPDATE_TOOLSNAPS=true go test ./...` to create snapshot
194
-
5. Run `script/generate-docs` to update README
195
-
6. Run `script/lint` and `script/test` before committing
196
-
7. If e2e tests are relevant, update `e2e/e2e_test.go` using existing test style
197
-
8. Commit code + snapshots + README changes together
192
+
3. Update the relevant bundled skill, or add a reasoned exemption in `pkg/skills/catalog/availability_test.go`. Every tool must be covered or explicitly exempted.
193
+
4. Write unit tests following the tool test pattern
194
+
5. Run `UPDATE_TOOLSNAPS=true go test ./...` to create snapshot
195
+
6. Run `script/generate-docs` to update README
196
+
7. Run `script/lint` and `script/test` before committing
197
+
8. If e2e tests are relevant, update `e2e/e2e_test.go` using existing test style
198
+
9. Commit code + snapshots + README changes together
199
+
200
+
When adding or changing a toolset `InstructionsFunc`, update the associated
201
+
skills as well: skills mode suppresses those instructions. The
202
+
`TestToolsetInstructionsAreCoveredBySkills` failure names the skills to revisit;
203
+
after updating them, refresh its digest with
204
+
`UPDATE_SKILLS_INSTRUCTIONS=true go test ./pkg/github -run TestToolsetInstructionsAreCoveredBySkills -count=1`.
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,6 +61,7 @@ For UI dependency upgrades, compare all four views (`get-me`, `issue-write`, `pr
61
61
- If renaming a tool, add a deprecation alias (see [Tool Renaming Guide](docs/tool-renaming.md))
62
62
- For toolset and icon configuration, see [Toolsets and Icons Guide](docs/toolsets-and-icons.md)
63
63
- For typed tool registration and compatibility schemas, see [Typed Tool Schemas](docs/typed-tool-schemas.md)
64
+
- When adding or changing tools or toolset instructions, update the relevant bundled skills or record why no skill applies. Run `go test ./pkg/skills/catalog -run TestCatalogToolRequirementsAreRegistered -count=1`; if the instruction snapshot fails, update the named skills and refresh it with `UPDATE_SKILLS_INSTRUCTIONS=true go test ./pkg/github -run TestToolsetInstructionsAreCoveredBySkills -count=1`. Run `script/generate-docs` to refresh the README catalog.
64
65
6. Push to your fork and [submit a pull request][pr] targeting the `main` branch
65
66
7. Pat yourself on the back and wait for your pull request to be reviewed and merged.
Copy file name to clipboardExpand all lines: README.md
+30Lines changed: 30 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -627,6 +627,34 @@ The following sets of tools are available:
627
627
|`copilot_spaces`| Copilot Spaces related tools |
628
628
|`github_support_docs_search`| Search docs to answer GitHub product and support questions |
629
629
630
+
## MCP Skills
631
+
632
+
The local server bundles workflow skills that replace server instructions when
633
+
enabled with `--features=skills` (or Insiders Mode). Skills are off by default
634
+
and are filtered to the tools available in the connection, so a restricted
635
+
toolset may expose only part of the catalog.
636
+
637
+
<!-- START AUTOMATED SKILLS -->
638
+
-[`account-and-team-context`](pkg/skills/catalog/skills/account-and-team-context/SKILL.md) — USE FOR: establishing who the authenticated account is, which organisations and teams it belongs to, who sits on a team, and who has write access to a repository. NOT FOR: finding an unfamiliar repository, or choosing what work to do next.
639
+
-[`codebase-exploration`](pkg/skills/catalog/skills/codebase-exploration/SKILL.md) — USE FOR: understanding an unfamiliar repository and how it got that way — its layout, where a behaviour is implemented, and when and why a particular function or line last changed. NOT FOR: editing files, or assessing whether a project is healthy overall.
640
+
-[`copilot-task-delegation`](pkg/skills/catalog/skills/copilot-task-delegation/SKILL.md) — USE FOR: handing a piece of work to the Copilot coding agent — judging whether an issue is scoped tightly enough to delegate, launching it, and asking for an automated first-pass review of a proposed change. NOT FOR: doing the work directly, or reviewing what comes back.
641
+
-[`discussion-participation`](pkg/skills/catalog/skills/discussion-participation/SKILL.md) — USE FOR: taking part in GitHub Discussions — finding the unanswered questions in a category, reading a thread in full, replying to it, and marking the reply that resolved it. NOT FOR: commenting on an issue or a proposed change, or working through a backlog.
642
+
-[`issue-authoring`](pkg/skills/catalog/skills/issue-authoring/SKILL.md) — USE FOR: filing one clear bug report or feature request — checking it is not already reported, choosing its type and fields, breaking it into sub-issues, and giving it a title and body someone can act on. NOT FOR: working through an existing backlog, or discussing an open question with a community.
643
+
-[`issue-backlog-triage`](pkg/skills/catalog/skills/issue-backlog-triage/SKILL.md) — USE FOR: triaging a backlog of open GitHub issues — judging which are actionable, labelling and typing them, linking duplicates and parents, and closing what is dead. NOT FOR: writing one new issue, scheduling committed work, or reviewing pull requests.
644
+
-[`label-scheme-management`](pkg/skills/catalog/skills/label-scheme-management/SKILL.md) — USE FOR: curating the label vocabulary a repository uses — adding ones it lacks, auditing which are actually applied, renaming and recolouring them, merging overlapping ones, and tidying away the unused. NOT FOR: applying an existing label to an issue, or deciding which issues matter.
645
+
-[`notification-triage`](pkg/skills/catalog/skills/notification-triage/SKILL.md) — USE FOR: working through a GitHub notification inbox — deciding what needs a reply, what to unsubscribe from, and what to mark read or done. NOT FOR: triaging a repository issue backlog, or answering review threads on one specific pull request.
646
+
-[`project-planning`](pkg/skills/catalog/skills/project-planning/SKILL.md) — USE FOR: planning and updating work on a GitHub Projects board — reading fields and views, adding issues or pull requests as items, setting status and iteration, and posting a status update. NOT FOR: triaging a repository issue backlog, or preparing a release.
647
+
-[`pull-request-authoring`](pkg/skills/catalog/skills/pull-request-authoring/SKILL.md) — USE FOR: taking a branch of work through to landed — opening the pull request, describing it, requesting reviewers, keeping it current with its base, and merging it once checks and approvals are in. NOT FOR: reviewing someone else's proposal, or acting on review comments left on yours.
648
+
-[`pull-request-code-review`](pkg/skills/catalog/skills/pull-request-code-review/SKILL.md) — USE FOR: examining someone else's pull request and delivering a verdict — reading the diff in context, leaving line-anchored comments as a batch, and approving or requesting changes. NOT FOR: replying to review comments left on your own change, or opening and merging one.
649
+
-[`pull-request-review-feedback`](pkg/skills/catalog/skills/pull-request-review-feedback/SKILL.md) — USE FOR: working through review feedback left on a pull request — reading each unresolved thread, deciding what to change, replying to the reviewer, and resolving threads. NOT FOR: producing a review of a pull request, merging one, or clearing a notification inbox.
650
+
-[`release-preparation`](pkg/skills/catalog/skills/release-preparation/SKILL.md) — USE FOR: cutting a release of a repository — picking the version, assembling the changelog since the last tag, confirming the branch is releasable, and drafting release notes. NOT FOR: assessing overall repository health, triaging security alerts, or working an issue backlog.
651
+
-[`repository-content-changes`](pkg/skills/catalog/skills/repository-content-changes/SKILL.md) — USE FOR: changing what a repository holds or whether it exists at all — opening a working branch, committing files remotely, deleting what should go, and creating, forking or removing the repository itself. NOT FOR: proposing those changes for review, or reading code you do not intend to touch.
652
+
-[`repository-discovery`](pkg/skills/catalog/skills/repository-discovery/SKILL.md) — USE FOR: finding a library, tool or organisation you cannot yet name, judging whether a candidate project is worth depending on, and keeping a starred shortlist useful. NOT FOR: searching inside a repository you have already chosen, or setting one up.
653
+
-[`repository-health-review`](pkg/skills/catalog/skills/repository-health-review/SKILL.md) — USE FOR: judging how well a repository is maintained overall — release cadence, branch and proposal age, issue inflow, build reliability, how many people can maintain it, and outstanding alert counts. NOT FOR: acting on any individual issue, alert or proposed change, or cutting a specific release.
654
+
-[`security-alert-triage`](pkg/skills/catalog/skills/security-alert-triage/SKILL.md) — USE FOR: investigating GitHub security alerts — code scanning, Dependabot, secret scanning and advisories — and deciding what to fix now, schedule, dismiss, or escalate. NOT FOR: summarising overall repository health, or reviewing feedback on a pull request.
655
+
-[`workflow-failure-triage`](pkg/skills/catalog/skills/workflow-failure-triage/SKILL.md) — USE FOR: diagnosing a failing GitHub Actions workflow run — a build gone red, which jobs failed, what their logs say, where the failing step is, and whether a rerun is justified. NOT FOR: judging long-term reliability trends across a repository, or deciding whether a change is ready to ship.
656
+
<!-- END AUTOMATED SKILLS -->
657
+
630
658
## Tools
631
659
632
660
Repository tools expose output schemas and typed `structuredContent` when the negotiated MCP protocol version is a supported version `2026-07-28` or newer. Older clients, clients with an unknown protocol version, and clients omitting the version receive the existing content without an output schema or structured output. Unknown versions are not treated as supported merely because they sort after `2026-07-28`.
@@ -1596,11 +1624,13 @@ For negotiated supported protocol versions `2026-07-28` or newer, the consolidat
1596
1624
-**get_secret_scanning_alert** - Get secret scanning alert
1597
1625
-**OAuth Challenge Scopes**: `security_events`
1598
1626
-`alertNumber`: The number of the alert. (number, required)
1627
+
-`hide_secret`: Whether to exclude the secret value from the response. Defaults to false. (boolean, optional)
1599
1628
-`owner`: The owner of the repository. (string, required)
1600
1629
-`repo`: The name of the repository. (string, required)
1601
1630
1602
1631
-**list_secret_scanning_alerts** - List secret scanning alerts
1603
1632
-**OAuth Challenge Scopes**: `security_events`
1633
+
-`hide_secret`: Whether to exclude secret values from the response. Defaults to false. (boolean, optional)
1604
1634
-`owner`: The owner of the repository. (string, required)
1605
1635
-`page`: Page number for pagination (min 1) (number, optional)
1606
1636
-`perPage`: Results per page for pagination (min 1, max 100) (number, optional)
0 commit comments