github

Route GitHub workflow requests to sub-skills for PRs, issues, discussions, and repository management.

6|1|Updated May 11, 2026
One-click install
npx skills add https://github.com/yakeworld/Synthos --skill github-yakeworld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/yakeworld/Synthos/tree/main/skills/extended/external-automation/automation-skills/github
Command: npx skills add https://github.com/yakeworld/Synthos --skill github-yakeworld

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It provides a single entry point for GitHub automation tasks by routing each request to the correct specialized sub-skill, so users do not need to know which of the seven child skills handles PRs, issues, discussions, authentication, code review, repository management, or codebase inspection. ## Core Features & Use Cases - Parent Routing Index: Validates the input contract (request string plus context with owner/repo) and delegates to one of seven sub-skills via the Hermes skill loading mechanism. - Sub-Skill Coverage: Includes codebase-inspection (pygount LOC analysis), github-auth, github-code-review, github-discussions (GraphQL-based), github-issues, github-pr-workflow, and github-repo-management. - Safe Error Handling: Rejects unknown sub-skill names and incomplete contexts with structured errors containing context and recovery hints, verified by a golden test set. - Use Case: A user asks to search open discussions about self-evolution in a repository; the parent skill validates owner/repo context and delegates to github-discussions, which runs the GraphQL query. ## Quick Start Ask the agent to handle a GitHub task such as listing open issues or creating a discussion in a specific owner/repo, and it will route the request to the matching sub-skill automatically.

Frequently Asked Questions about github

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a GitHub Discussion with the gh CLI?

Creating a GitHub Discussion requires the GraphQL createDiscussion mutation because the REST POST endpoint returns 404. First query the repository and category node IDs via GraphQL, then submit the mutation, writing long bodies to a temp JSON file with proper escaping.

How do I count lines of code in a repository?

Use pygount with --format=summary and --folders-to-skip to exclude .git, node_modules, and venv directories. It reports language breakdown, file counts, code lines, and comment lines; use --suffix to filter specific languages.

Why does the GitHub Discussions REST API return 404 on POST?

GitHub's REST API only supports GET operations for discussions, so POST always returns 404. All creation and comment operations must use GraphQL mutations with node IDs rather than REST integer IDs.

What happens when a request is missing owner or repo context?

The parent skill rejects the request with a contract_incomplete error that names the missing fields and includes a recovery hint with a retry template. It never forwards incomplete contexts to sub-skills or fabricates default values.

Can this skill handle unknown or unsupported GitHub sub-skill names?

No. Requests targeting sub-skills outside the seven registered names are rejected with an unknown_subskill error containing context and recovery suggestions. The skill never guesses routes or executes unverified state-changing operations.