Reports progress back to the master repository (octocat-supply-platform). Use this when creating PRs for issues that reference octocat-supply-platform, or when completing tasks spawned from the master repo.
This skill requires the GitHub MCP Server configured on this repo so Copilot coding agent can comment on issues in octocat-supply-platform.
| Step | Action |
|---|---|
| 1 | Go to Settings → Copilot → Coding agent → MCP configuration and add the GitHub MCP server JSON config |
| 2 | Use https://api.githubcopilot.com/mcp as the server URL (not /readonly) for write access |
| 3 | Include issues in the X-MCP-Toolsets header |
| 4 | Add a GitHub PAT as COPILOT_MCP_GITHUB_PERSONAL_ACCESS_TOKEN in the repo's Copilot environment secrets |
| 5 | Instruct the agent in your issue to report progress back to the master issue |
MCP Configuration JSON:
{
"mcpServers": {
"github": {
"url": "https://api.githubcopilot.com/mcp",
"headers": {
"X-MCP-Toolsets": "issues"
}
}
}
}
When working on issues that were spawned from octocat-supply-platform, follow this process to maintain traceability:
Look for issue titles or bodies containing:
[octocat-supply-platform#<NUMBER>]your-org/octocat-supply-platform#<NUMBER>Spawned from octocat-supply-platformExtract the master issue number from these references.
When creating a PR, use this title format:
[octocat-supply-platform#<ISSUE_NUMBER>] <Descriptive title>
In the PR body, include:
## Related Issues
- Master: your-org/octocat-supply-platform#<ISSUE_NUMBER>
- This repo: #<LOCAL_ISSUE_NUMBER>
## Changes
<Description of changes — React components, routes, Tailwind styling, etc.>
## Cross-Repo Dependencies
- Depends on: <list any PRs in octocat-supply-api this depends on>
- Required by: <list any PRs that depend on this>
After creating the PR, use the add_issue_comment tool to comment on the master issue:
## 🔗 PR Created in octocat-supply-web
**PR:** your-org/octocat-supply-web#<PR_NUMBER>
**Status:** Ready for review
**CI:** Pending
### Summary
<Brief description of React / frontend changes>
### Integration Notes
<Any notes about dependencies on API or shared types>
When your PR is merged, update the master issue:
## ✅ PR Merged in octocat-supply-web
**PR:** your-org/octocat-supply-web#<PR_NUMBER> has been merged.
Frontend component is now complete for this feature.