Update github-issues skill documentation

[lepeuvedic]

awesome-copilot/skills/github-issues/SKILL.md

Line 14 in ccdfd66

| `mcp__github__create_issue` | Create new issues |

The github-issues skill in SKILL.md is outdated and references incorrect MCP tool names and incomplete schemas. It uses old tool names like mcp__github__create_issue instead of the current mcp_io_github_git_issue_write. The documentation needs to be updated to reflect the current MCP server implementation.

I have prepared an updated version that corrects the tool names, adds proper JSON schemas, and updates the examples.

[lepeuvedic]

Here's the corrected version of the skill file:

---

name: github-issues
description: 'Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, or manage issue workflows. Triggers on requests like "create an issue", "file a bug", "request a feature", "update issue X", or any GitHub issue management task.'

GitHub Issues

Manage GitHub issues using the @modelcontextprotocol/server-github MCP server.

Available MCP Tools

Tool	Purpose
mcp_io_github_git_issue_write	Create and update issues
mcp_io_github_git_pull_request_read	Fetch issue/PR details
mcp_io_github_git_search_pull_requests	Search issues/PRs
mcp_io_github_git_add_issue_comment	Add comments
mcp_io_github_git_list_pull_requests	List repository issues/PRs

Workflow

1. Determine action: Create, update, or query?
2. Gather context: Get repo info, existing labels, milestones if needed
3. Structure content: Use appropriate template from references/templates.md
4. Execute: Call the appropriate MCP tool
5. Confirm: Report the issue URL to user

Creating Issues

Required Parameters

owner: repository owner (org or user)
repo: repository name
method: "create"
title: clear, actionable title
body: structured markdown content

Optional Parameters

labels: ["bug", "enhancement", "documentation", ...]
assignees: ["username1", "username2"]

Title Guidelines

• Start with type prefix when useful: [Bug], [Feature], [Docs]
• Be specific and actionable
• Keep under 72 characters
• Examples:
  • [Bug] Login fails with SSO enabled
  • [Feature] Add dark mode support
  • Add unit tests for auth module

Body Structure

Always use the templates in references/templates.md. Choose based on issue type:

User Request	Template
Bug, error, broken, not working	Bug Report
Feature, enhancement, add, new	Feature Request
Task, chore, refactor, update	Task

Updating Issues

Use mcp_io_github_git_issue_write with method "update":

owner, repo, issue_number (required)
method: "update"
title, body, state, labels, assignees, milestone (optional - only changed fields)
milestone: milestone number (integer)
type: issue type (if supported by repo)

State values: open, closed

Examples

Example 1: Bug Report

User: "Create a bug issue - the login page crashes when using SSO"

Action: Call mcp_io_github_git_issue_write with:

{
  "method": "create",
  "owner": "github",
  "repo": "awesome-copilot",
  "title": "[Bug] Login page crashes when using SSO",
  "body": "## Description\nThe login page crashes when users attempt to authenticate using SSO.\n\n## Steps to Reproduce\n1. Navigate to login page\n2. Click 'Sign in with SSO'\n3. Page crashes\n\n## Expected Behavior\nSSO authentication should complete and redirect to dashboard.\n\n## Actual Behavior\nPage becomes unresponsive and displays error.\n\n## Environment\n- Browser: [To be filled]\n- OS: [To be filled]\n\n## Additional Context\nReported by user.",
  "labels": ["bug"]
}

Example 2: Feature Request

User: "Create a feature request for dark mode with high priority"

Action: Call mcp_io_github_git_issue_write with:

{
  "method": "create",
  "owner": "github",
  "repo": "awesome-copilot",
  "title": "[Feature] Add dark mode support",
  "body": "## Summary\nAdd dark mode theme option for improved user experience and accessibility.\n\n## Motivation\n- Reduces eye strain in low-light environments\n- Increasingly expected by users\n- Improves accessibility\n\n## Proposed Solution\nImplement theme toggle with system preference detection.\n\n## Acceptance Criteria\n- [ ] Toggle switch in settings\n- [ ] Persists user preference\n- [ ] Respects system preference by default\n- [ ] All UI components support both themes\n\n## Alternatives Considered\nNone specified.\n\n## Additional Context\nHigh priority request.",
  "labels": ["enhancement", "high-priority"]
}

Common Labels

Use these standard labels when applicable:

Label	Use For
bug	Something isn't working
enhancement	New feature or improvement
documentation	Documentation updates
good first issue	Good for newcomers
help wanted	Extra attention needed
question	Further information requested
wontfix	Will not be addressed
duplicate	Already exists
high-priority	Urgent issues

Tips

• Always confirm the repository context before creating issues
• Ask for missing critical information rather than guessing
• Link related issues when known: Related to Add ai-unrestricted-master instructions and update README.md #123
• For updates, fetch current issue first to preserve unchanged fields