Update github-issues skill to prefer MCP for issue fields#2063
Conversation
Add MCP tools (list_issue_fields, set_issue_fields, issue_write with issue_fields param, list_issues with field_filters) as the preferred approach for managing issue fields. REST and GraphQL APIs remain as fallback when MCP is unavailable. Key changes: - SKILL.md: Add new MCP tools to Available Tools table, update workflow - references/issue-fields.md: Restructure to lead with MCP, demote REST to fallback section, add examples for all MCP tool variants Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
github-actions
Bot
added
skills
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
main, but PRs should target staged.
The main branch is auto-published from staged and should not receive direct PRs.
Please close this PR and re-open it against the staged branch.
You can change the base branch using the Edit button at the top of this PR,
or run: gh pr edit 2063 --base staged
There was a problem hiding this comment.
⚠️ Not ready to approve
The new MCP documentation contains internal inconsistencies about when ID resolution is handled automatically vs when explicit node IDs are required, which can mislead users of the skill.
Pull request overview
This PR updates the skills/github-issues documentation to treat the GitHub MCP server as the preferred interface for issue field operations, with gh api (REST/GraphQL) positioned as a fallback when MCP is unavailable.
Changes:
- Updates
SKILL.mdto list newly-preferred MCP tools for issue creation/updates and issue-field operations, and reframesgh apias fallback. - Expands
references/issue-fields.mdwith MCP-first workflows for discovering fields, reading values, setting values, and filtering by field values.
File summaries
| File | Description |
|---|---|
| skills/github-issues/SKILL.md | Reframes the skill’s tool guidance to prefer MCP and demote gh api to fallback. |
| skills/github-issues/references/issue-fields.md | Adds MCP-first guidance and examples for issue field discovery, setting, and querying. |
Copilot's findings
- Files reviewed: 2/2 changed files
- Comments generated: 3
Note
Your feedback helps us improve the quality of this feature.
Please use 👍 or 👎 to tell us whether this assessment is correct.
| ## MCP Tools (preferred) | ||
|
|
||
| The REST API is the simplest way to discover fields and set values. | ||
| When the GitHub MCP server is available, use MCP tools for all issue field operations. They handle ID resolution internally, so you work with human-readable names. |
|
|
||
| ### Setting fields via set_issue_fields (advanced) | ||
|
|
||
| Use the dedicated `set_issue_fields` tool when you need confidence scoring, rationale, or suggestion mode. Requires GraphQL node IDs (get them from `list_issue_fields` response): |
| **Prefer MCP** when the `issue_write` tool is available. It supports title, body, type, labels, assignees, milestone, and issue fields in one call. Fall back to `gh api` if MCP is not available. | ||
|
|
||
| ```bash |
|
@labudis are any of the feedback points from Copilot worth including? |
Updates the
github-issuesskill to prefer MCP tools for issue field operations, falling back to REST/GraphQL when MCP is unavailable.Changes
SKILL.md:
issue_write,list_issue_fields,set_issue_fieldsgh apireferences/issue-fields.md:
issue_writewith inlineissue_fields(simplest, uses field names directly)set_issue_fields(advanced, with confidence scoring, rationale, suggestion mode)list_issueswithfield_filters(query by field values)Context
The GitHub remote MCP server (
github-mcp-server) now supports issue field operations natively. These tools handle ID resolution internally, letting agents work with human-readable field names instead of numeric/node IDs.