github
Manage GitHub issues, PRs, branches, and repositories via OAuth (3LO). For reading issues or PR details, not for deep code analysis — delegate that to code-agent.
What this skill does
# GitHub
## Available Tools
**Read**
- **github_search_repos(query, max_results?)**: Search GitHub repositories.
- **github_get_repo(owner, repo)**: Get repository details (description, stars, language, topics).
- **github_list_issues(owner, repo, state?, labels?, max_results?)**: List issues. `state`: open | closed | all.
- **github_get_issue(owner, repo, issue_number)**: Get a single issue with comments.
- **github_list_pulls(owner, repo, state?, max_results?)**: List pull requests.
- **github_get_pull(owner, repo, pull_number)**: Get a single pull request with diff summary.
- **github_get_file(owner, repo, path, ref?)**: Get file contents. `ref` defaults to default branch.
- **github_search_code(query, max_results?)**: Search code across GitHub (use `repo:owner/name` to scope).
**Write** *(requires user approval)*
- **github_create_branch(owner, repo, branch, from_branch?)**: Create a new branch.
- **github_push_files(owner, repo, branch, files, message)**: Create or update files. `files`: list of `{path, content}`.
- **github_create_pull_request(owner, repo, title, body, head, base?)**: Open a pull request.
## Usage Guidelines
- **Never perform write operations autonomously.** Only call `github_create_branch`, `github_push_files`, or `github_create_pull_request` when the user has explicitly requested or approved the action. If the user's intent is ambiguous, ask for confirmation before proceeding.
- Always read existing files with `github_get_file` before modifying them.
- Before calling any write tool, explain exactly what will change (branch name, target files, PR details) and wait for user agreement.
- For multi-file changes: create a branch → push all files in one `github_push_files` call → open PR.
- Use `github_search_code` with `repo:owner/name` qualifier to scope searches to a specific repository.
## UI Guidance (from tools-config)
**GitHub Tool Usage:**
- github_search_repos: Search GitHub repositories by keyword
- github_get_repo: Get repository details (description, stars, language, topics)
- github_list_issues: List issues (state: open|closed|all, filter by labels)
- github_get_issue: Get a single issue with all comments
- github_list_pulls: List pull requests
- github_get_pull: Get a single PR with diff summary
- github_get_file: Read file contents from a repo (specify ref/branch if needed)
- github_search_code: Search code across GitHub (use repo:owner/name to scope)
- github_create_branch: Create a new branch (write — requires approval)
- github_push_files: Create or update files on a branch (write — requires approval)
- github_create_pull_request: Open a pull request (write — requires approval)
**Write workflow:**
1. github_get_file to read existing files before modifying
2. github_create_branch to create a feature branch
3. github_push_files to commit all changes in one call
4. github_create_pull_request to open a PR
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.