composio-github

name	composio-github
description	Triage and orient GitHub repository, pull request, and issue work through Composio-connected GitHub. Use when the user asks for general GitHub help, PR or issue summaries, repository context, or needs to choose a more specific GitHub workflow before acting.

GitHub via Composio

Overview

Umbrella entrypoint for GitHub work through Composio meta-tools.

This integration is intentionally hybrid:

• Prefer Composio GitHub tools for issues, PRs, comments, labels, and structured repo reads when connected.
• Use local git and gh for current-branch discovery, commits/pushes, auth status, and Actions log inspection when the connector does not cover it well.
• Keep connector state and local checkout context aligned.

Specialist routing

Category	Skill / path
What needs attention on PRs/issues	composio:composio-github-pr-triage
Review comment follow-up	local analysis + connector comments; optional gh
CI / Actions logs	local gh run view/log (not assumed in connector)
Commit/push/open PR from branch	local git + gh

Default Workflow

1. Resolve repo / PR / issue scope (URL, number, or local git remote).
2. composio_status if GitHub connection uncertain.
3. composio_search for the structured action needed.
4. Execute reads, summarize, then only mutate with clear intent + confirm policy.
5. Route to specialist triage when the user wants attention ranking.

Write Safety

• Restate exact PR/issue targets before mutations.
• Merging, force-pushing, deleting, closing: explicit intent + confirmed=true unless yolo.
• Do not imply Actions logs came from Composio if you used gh.

Output Expectations

• Concise repo/PR/issue state + next action
• Note connector vs local gh sources
• For mixed requests, say which path you are taking

Example Requests

• "Summarize open PRs that need attention."
• "What's going on in issue 482?"
• "Draft a PR description from the current branch." (local git + optional connector PR create)