[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AG21JS36B02WEYRNVTRTBE":3,"skill-same:01M6AG21JS36B02WEYRNVTRTBE":93},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":26,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M6AG21JS36B02WEYRNVTRTBE","github-automation",null,"Automate GitHub repositories, issues, pull requests, branches, CI\u002FCD, and permissions via Rube MCP (Composio). Manage code workflows, review PRs, search code, and handle deployments programmatically.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33481,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fgithub-automation\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"github","automation","github automation","search","2026","review prs","code workflows","CI\u002FCD","critical","branches","composio","community","ci","MCP","pull","issues","permissions","code","pull requests","workflows","review","2026-11-10 10:12:30",false,"---\nname: github-automation\ndescription: \"Automate GitHub repositories, issues, pull requests, branches, CI\u002FCD, and permissions via Rube MCP (Composio). Manage code workflows, review PRs, search code, and handle deployments programmatically.\"\nmetadata:\n  risk: critical\n  source: community\n  date_added: \"2026-02-27\"\n---\n\n# GitHub Automation via Rube MCP\n\nAutomate GitHub repository management, issue tracking, pull request workflows, branch operations, and CI\u002FCD through Composio's GitHub toolkit.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active GitHub connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `github`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `github`\n3. If connection is not ACTIVE, follow the returned auth link to complete GitHub OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Create and Manage Issues\n\n**When to use**: User wants to create, list, or manage GitHub issues\n\n**Tool sequence**:\n1. `GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER` - Find target repo if unknown [Prerequisite]\n2. `GITHUB_LIST_REPOSITORY_ISSUES` - List existing issues (includes PRs) [Required]\n3. `GITHUB_CREATE_AN_ISSUE` - Create a new issue [Required]\n4. `GITHUB_CREATE_AN_ISSUE_COMMENT` - Add comments to an issue [Optional]\n5. `GITHUB_SEARCH_ISSUES_AND_PULL_REQUESTS` - Search across repos by keyword [Optional]\n\n**Key parameters**:\n- `owner`: Repository owner (username or org), case-insensitive\n- `repo`: Repository name without .git extension\n- `title`: Issue title (required for creation)\n- `body`: Issue description (supports Markdown)\n- `labels`: Array of label names\n- `assignees`: Array of GitHub usernames\n- `state`: 'open', 'closed', or 'all' for filtering\n\n**Pitfalls**:\n- `GITHUB_LIST_REPOSITORY_ISSUES` returns both issues AND pull requests; check `pull_request` field to distinguish\n- Only users with push access can set assignees, labels, and milestones; they are silently dropped otherwise\n- Pagination: `per_page` max 100; iterate pages until empty\n\n### 2. Manage Pull Requests\n\n**When to use**: User wants to create, review, or merge pull requests\n\n**Tool sequence**:\n1. `GITHUB_FIND_PULL_REQUESTS` - Search and filter PRs [Required]\n2. `GITHUB_GET_A_PULL_REQUEST` - Get detailed PR info including mergeable status [Required]\n3. `GITHUB_LIST_PULL_REQUESTS_FILES` - Review changed files [Optional]\n4. `GITHUB_CREATE_A_PULL_REQUEST` - Create a new PR [Required]\n5. `GITHUB_CREATE_AN_ISSUE_COMMENT` - Post review comments [Optional]\n6. `GITHUB_LIST_CHECK_RUNS_FOR_A_REF` - Verify CI status before merge [Optional]\n7. `GITHUB_MERGE_A_PULL_REQUEST` - Merge after explicit user approval [Required]\n\n**Key parameters**:\n- `head`: Source branch with changes (must exist; for cross-repo: 'username:branch')\n- `base`: Target branch to merge into (e.g., 'main')\n- `title`: PR title (required unless `issue` number provided)\n- `merge_method`: 'merge', 'squash', or 'rebase'\n- `state`: 'open', 'closed', or 'all'\n\n**Pitfalls**:\n- `GITHUB_CREATE_A_PULL_REQUEST` fails with 422 if base\u002Fhead are invalid, identical, or already merged\n- `GITHUB_MERGE_A_PULL_REQUEST` can be rejected if PR is draft, closed, or branch protection applies\n- Always verify mergeable status with `GITHUB_GET_A_PULL_REQUEST` immediately before merging\n- Require explicit user confirmation before calling MERGE\n\n### 3. Manage Repositories and Branches\n\n**When to use**: User wants to create repos, manage branches, or update repo settings\n\n**Tool sequence**:\n1. `GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER` - List user's repos [Required]\n2. `GITHUB_GET_A_REPOSITORY` - Get detailed repo info [Optional]\n3. `GITHUB_CREATE_A_REPOSITORY_FOR_THE_AUTHENTICATED_USER` - Create personal repo [Required]\n4. `GITHUB_CREATE_AN_ORGANIZATION_REPOSITORY` - Create org repo [Alternative]\n5. `GITHUB_LIST_BRANCHES` - List branches [Required]\n6. `GITHUB_CREATE_A_REFERENCE` - Create new branch from SHA [Required]\n7. `GITHUB_UPDATE_A_REPOSITORY` - Update repo settings [Optional]\n\n**Key parameters**:\n- `name`: Repository name\n- `private`: Boolean for visibility\n- `ref`: Full reference path (e.g., 'refs\u002Fheads\u002Fnew-branch')\n- `sha`: Commit SHA to point the new reference to\n- `default_branch`: Default branch name\n\n**Pitfalls**:\n- `GITHUB_CREATE_A_REFERENCE` only creates NEW references; use `GITHUB_UPDATE_A_REFERENCE` for existing ones\n- `ref` must start with 'refs\u002F' and contain at least two slashes\n- `GITHUB_LIST_BRANCHES` paginates via `page`\u002F`per_page`; iterate until empty page\n- `GITHUB_DELETE_A_REPOSITORY` is permanent and irreversible; requires admin privileges\n\n### 4. Search Code and Commits\n\n**When to use**: User wants to find code, files, or commits across repositories\n\n**Tool sequence**:\n1. `GITHUB_SEARCH_CODE` - Search file contents and paths [Required]\n2. `GITHUB_SEARCH_CODE_ALL_PAGES` - Multi-page code search [Alternative]\n3. `GITHUB_SEARCH_COMMITS_BY_AUTHOR` - Search commits by author\u002Fdate\u002Forg [Required]\n4. `GITHUB_LIST_COMMITS` - List commits for a specific repo [Alternative]\n5. `GITHUB_GET_A_COMMIT` - Get detailed commit info [Optional]\n6. `GITHUB_GET_REPOSITORY_CONTENT` - Get file content [Optional]\n\n**Key parameters**:\n- `q`: Search query with qualifiers (`language:python`, `repo:owner\u002Frepo`, `extension:js`)\n- `owner`\u002F`repo`: For repo-specific commit listing\n- `author`: Filter by commit author\n- `since`\u002F`until`: ISO 8601 date range for commits\n\n**Pitfalls**:\n- Code search only indexes files under 384KB on default branch\n- Maximum 1000 results returned from code search\n- `GITHUB_SEARCH_COMMITS_BY_AUTHOR` requires keywords in addition to qualifiers; qualifier-only queries are not allowed\n- `GITHUB_LIST_COMMITS` returns 409 on empty repos\n\n### 5. Manage CI\u002FCD and Deployments\n\n**When to use**: User wants to view workflows, check CI status, or manage deployments\n\n**Tool sequence**:\n1. `GITHUB_LIST_REPOSITORY_WORKFLOWS` - List GitHub Actions workflows [Required]\n2. `GITHUB_GET_A_WORKFLOW` - Get workflow details by ID or filename [Optional]\n3. `GITHUB_CREATE_A_WORKFLOW_DISPATCH_EVENT` - Manually trigger a workflow [Required]\n4. `GITHUB_LIST_CHECK_RUNS_FOR_A_REF` - Check CI status for a commit\u002Fbranch [Required]\n5. `GITHUB_LIST_DEPLOYMENTS` - List deployments [Optional]\n6. `GITHUB_GET_A_DEPLOYMENT_STATUS` - Get deployment status [Optional]\n\n**Key parameters**:\n- `workflow_id`: Numeric ID or filename (e.g., 'ci.yml')\n- `ref`: Git reference (branch\u002Ftag) for workflow dispatch\n- `inputs`: JSON string of workflow inputs matching `on.workflow_dispatch.inputs`\n- `environment`: Filter deployments by environment name\n\n**Pitfalls**:\n- `GITHUB_CREATE_A_WORKFLOW_DISPATCH_EVENT` requires the workflow to have `workflow_dispatch` trigger configured\n- Full path `.github\u002Fworkflows\u002Fmain.yml` is auto-stripped to just `main.yml`\n- Inputs max 10 key-value pairs; must match workflow's `on.workflow_dispatch.inputs` definitions\n\n### 6. Manage Users and Permissions\n\n**When to use**: User wants to check collaborators, permissions, or branch protection\n\n**Tool sequence**:\n1. `GITHUB_LIST_REPOSITORY_COLLABORATORS` - List repo collaborators [Required]\n2. `GITHUB_GET_REPOSITORY_PERMISSIONS_FOR_A_USER` - Check specific user's access [Optional]\n3. `GITHUB_GET_BRANCH_PROTECTION` - Inspect branch protection rules [Required]\n4. `GITHUB_UPDATE_BRANCH_PROTECTION` - Update protection settings [Optional]\n5. `GITHUB_ADD_A_REPOSITORY_COLLABORATOR` - Add\u002Fupdate collaborator [Optional]\n\n**Key parameters**:\n- `affiliation`: 'outside', 'direct', or 'all' for collaborator filtering\n- `permission`: Filter by 'pull', 'triage', 'push', 'maintain', 'admin'\n- `branch`: Branch name for protection rules\n- `enforce_admins`: Whether protection applies to admins\n\n**Pitfalls**:\n- `GITHUB_GET_BRANCH_PROTECTION` returns 404 for unprotected branches; treat as no protection rules\n- Determine push ability from `permissions.push` or `role_name`, not display labels\n- `GITHUB_LIST_REPOSITORY_COLLABORATORS` paginates; iterate all pages\n- `GITHUB_GET_REPOSITORY_PERMISSIONS_FOR_A_USER` may be inconclusive for non-collaborators\n\n## Common Patterns\n\n### ID Resolution\n- **Repo name -> owner\u002Frepo**: `GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER`\n- **PR number -> PR details**: `GITHUB_FIND_PULL_REQUESTS` then `GITHUB_GET_A_PULL_REQUEST`\n- **Branch name -> SHA**: `GITHUB_GET_A_BRANCH`\n- **Workflow name -> ID**: `GITHUB_LIST_REPOSITORY_WORKFLOWS`\n\n### Pagination\nAll list endpoints use page-based pagination:\n- `page`: Page number (starts at 1)\n- `per_page`: Results per page (max 100)\n- Iterate until response returns fewer results than `per_page`\n\n### Safety\n- Always verify PR mergeable status before merge\n- Require explicit user confirmation for destructive operations (merge, delete)\n- Check CI status with `GITHUB_LIST_CHECK_RUNS_FOR_A_REF` before merging\n\n## Known Pitfalls\n\n- **Issues vs PRs**: `GITHUB_LIST_REPOSITORY_ISSUES` returns both; check `pull_request` field\n- **Pagination limits**: `per_page` max 100; always iterate pages until empty\n- **Branch creation**: `GITHUB_CREATE_A_REFERENCE` fails with 422 if reference already exists\n- **Merge guards**: Merge can fail due to branch protection, failing checks, or draft status\n- **Code search limits**: Only files \u003C384KB on default branch; max 1000 results\n- **Commit search**: Requires search text keywords alongside qualifiers\n- **Destructive actions**: Repo deletion is irreversible; merge cannot be undone\n- **Silent permission drops**: Labels, assignees, milestones silently dropped without push access\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List repos | `GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER` | `type`, `sort`, `per_page` |\n| Get repo | `GITHUB_GET_A_REPOSITORY` | `owner`, `repo` |\n| Create issue | `GITHUB_CREATE_AN_ISSUE` | `owner`, `repo`, `title`, `body` |\n| List issues | `GITHUB_LIST_REPOSITORY_ISSUES` | `owner`, `repo`, `state` |\n| Find PRs | `GITHUB_FIND_PULL_REQUESTS` | `repo`, `state`, `author` |\n| Create PR | `GITHUB_CREATE_A_PULL_REQUEST` | `owner`, `repo`, `head`, `base`, `title` |\n| Merge PR | `GITHUB_MERGE_A_PULL_REQUEST` | `owner`, `repo`, `pull_number`, `merge_method` |\n| List branches | `GITHUB_LIST_BRANCHES` | `owner`, `repo` |\n| Create branch | `GITHUB_CREATE_A_REFERENCE` | `owner`, `repo`, `ref`, `sha` |\n| Search code | `GITHUB_SEARCH_CODE` | `q` |\n| List commits | `GITHUB_LIST_COMMITS` | `owner`, `repo`, `author`, `since` |\n| Search commits | `GITHUB_SEARCH_COMMITS_BY_AUTHOR` | `q` |\n| List workflows | `GITHUB_LIST_REPOSITORY_WORKFLOWS` | `owner`, `repo` |\n| Trigger workflow | `GITHUB_CREATE_A_WORKFLOW_DISPATCH_EVENT` | `owner`, `repo`, `workflow_id`, `ref` |\n| Check CI | `GITHUB_LIST_CHECK_RUNS_FOR_A_REF` | `owner`, `repo`, ref |\n| List collaborators | `GITHUB_LIST_REPOSITORY_COLLABORATORS` | `owner`, `repo` |\n| Branch protection | `GITHUB_GET_BRANCH_PROTECTION` | `owner`, `repo`, `branch` |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# GitHub Automation via Rube MCP\n\nAutomate GitHub repository management, issue tracking, pull request workflows, branch operations, and CI\u002FCD through Composio's GitHub toolkit.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active GitHub connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `github`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `github`\n3. If connection is not ACTIVE, follow the returned auth link to complete GitHub OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Create and Manage Issues\n\n**When to use**: User wants to create, list, or manage GitHub issues\n\n**Tool sequence**:\n1. `GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER` - Find target repo if unknown [Prerequisite]\n2. `GITHUB_LIST_REPOSITORY_ISSUES` - List existing issues (includes PRs) [Required]\n3. `GITHUB_CREATE_AN_ISSUE` - Create a new issue [Required]\n4. `GITHUB_CREATE_AN_ISSUE_COMMENT` - Add comments to an issue [Optional]\n5. `GITHUB_SEARCH_ISSUES_AND_PULL_REQUESTS` - Search across repos by keyword [Optional]\n\n**Key parameters**:\n- `owner`: Repository owner (username or org), case-insensitive\n- `repo`: Repository name without .git extension\n- `title`: Issue title (required for creation)\n- `body`: Issue description (supports Markdown)\n- `labels`: Array of label names\n- `assignees`: Array of GitHub usernames\n- `state`: 'open', 'closed', or 'all' for filtering\n\n**Pitfalls**:\n- `GITHUB_LIST_REPOSITORY_ISSUES` returns both issues AND pull requests; check `pull_request` field to distinguish\n- Only users with push access can set assignees, labels, and milestones; they are silently dropped otherwise\n- Pagination: `per_page` max 100; iterate pages until empty\n\n### 2. Manage Pull Requests\n\n**When to use**: User wants to create, review, or merge pull requests\n\n**Tool sequence**:\n1. `GITHUB_FIND_PULL_REQUESTS` - Search and filter PRs [Required]\n2. `GITHUB_GET_A_PULL_REQUEST` - Get detailed PR info including mergeable status [Required]\n3. `GITHUB_LIST_PULL_REQUESTS_FILES` - Review changed files [Optional]\n4. `GITHUB_CREATE_A_PULL_REQUEST` - Create a new PR [Required]\n5. `GITHUB_CREATE_AN_ISSUE_COMMENT` - Post review comments [Optional]\n6. `GITHUB_LIST_CHECK_RUNS_FOR_A_REF` - Verify CI status before merge [Optional]\n7. `GITHUB_MERGE_A_PULL_REQUEST` - Merge after explicit user approval [Required]\n\n**Key parameters**:\n- `head`: Source branch with changes (must exist; for cross-repo: 'username:branch')\n- `base`: Target branch to merge into (e.g., 'main')\n- `title`: PR title (required unless `issue` number provided)\n- `merge_method`: 'merge', 'squash', or 'rebase'\n- `state`: 'open', 'closed', or 'all'\n\n**Pitfalls**:\n- `GITHUB_CREATE_A_PULL_REQUEST` fails with 422 if base\u002Fhead are invalid, identical, or already merged\n- `GITHUB_MERGE_A_PULL_REQUEST` can be rejected if PR is draft, closed, or branch protection applies\n- Always verify mergeable status with `GITHUB_GET_A_PULL_REQUEST` immediately before merging\n- Require explicit user confirmation before calling MERGE\n\n### 3. Manage Repositories and Branches\n\n**When to use**: User wants to create repos, manage branches, or update repo settings\n\n**Tool sequence**:\n1. `GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER` - List user's repos [Required]\n2. `GITHUB_GET_A_REPOSITORY` - Get detailed repo info [Optional]\n3. `GITHUB_CREATE_A_REPOSITORY_FOR_THE_AUTHENTICATED_USER` - Create personal repo [Required]\n4. `GITHUB_CREATE_AN_ORGANIZATION_REPOSITORY` - Create org repo [Alternative]\n5. `GITHUB_LIST_BRANCHES` - List branches [Required]\n6. `GITHUB_CREATE_A_REFERENCE` - Create new branch from SHA [Required]\n7. `GITHUB_UPDATE_A_REPOSITORY` - Update repo settings [Optional]\n\n**Key parameters**:\n- `name`: Repository name\n- `private`: Boolean for visibility\n- `ref`: Full reference path (e.g., 'refs\u002Fheads\u002Fnew-branch')\n- `sha`: Commit SHA to point the new reference to\n- `default_branch`: Default branch name\n\n**Pitfalls**:\n- `GITHUB_CREATE_A_REFERENCE` only creates NEW references; use `GITHUB_UPDATE_A_REFERENCE` for existing ones\n- `ref` must start with 'refs\u002F' and contain at least two slashes\n- `GITHUB_LIST_BRANCHES` paginates via `page`\u002F`per_page`; iterate until empty page\n- `GITHUB_DELETE_A_REPOSITORY` is permanent and irreversible; requires admin privileges\n\n### 4. Search Code and Commits\n\n**When to use**: User wants to find code, files, or commits across repositories\n\n**Tool sequence**:\n1. `GITHUB_SEARCH_CODE` - Search file contents and paths [Required]\n2. `GITHUB_SEARCH_CODE_ALL_PAGES` - Multi-page code search [Alternative]\n3. `GITHUB_SEARCH_COMMITS_BY_AUTHOR` - Search commits by author\u002Fdate\u002Forg [Required]\n4. `GITHUB_LIST_COMMITS` - List commits for a specific repo [Alternative]\n5. `GITHUB_GET_A_COMMIT` - Get detailed commit info [Optional]\n6. `GITHUB_GET_REPOSITORY_CONTENT` - Get file content [Optional]\n\n**Key parameters**:\n- `q`: Search query with qualifiers (`language:python`, `repo:owner\u002Frepo`, `extension:js`)\n- `owner`\u002F`repo`: For repo-specific commit listing\n- `author`: Filter by commit author\n- `since`\u002F`until`: ISO 8601 date range for commits\n\n**Pitfalls**:\n- Code search only indexes files under 384KB on default branch\n- Maximum 1000 results returned from code search\n- `GITHUB_SEARCH_COMMITS_BY_AUTHOR` requires keywords in addition to qualifiers; qualifier-only queries are not allowed\n- `GITHUB_LIST_COMMITS` returns 409 on empty repos\n\n### 5. Manage CI\u002FCD and Deployments\n\n**When to use**: User wants to view workflows, check CI status, or manage deployments\n\n**Tool sequence**:\n1. `GITHUB_LIST_REPOSITORY_WORKFLOWS` - List GitHub Actions workflows [Required]\n2. `GITHUB_GET_A_WORKFLOW` - Get workflow details by ID or filename [Optional]\n3. `GITHUB_CREATE_A_WORKFLOW_DISPATCH_EVENT` - Manually trigger a workflow [Required]\n4. `GITHUB_LIST_CHECK_RUNS_FOR_A_REF` - Check CI status for a commit\u002Fbranch [Required]\n5. `GITHUB_LIST_DEPLOYMENTS` - List deployments [Optional]\n6. `GITHUB_GET_A_DEPLOYMENT_STATUS` - Get deployment status [Optional]\n\n**Key parameters**:\n- `workflow_id`: Numeric ID or filename (e.g., 'ci.yml')\n- `ref`: Git reference (branch\u002Ftag) for workflow dispatch\n- `inputs`: JSON string of workflow inputs matching `on.workflow_dispatch.inputs`\n- `environment`: Filter deployments by environment name\n\n**Pitfalls**:\n- `GITHUB_CREATE_A_WORKFLOW_DISPATCH_EVENT` requires the workflow to have `workflow_dispatch` trigger configured\n- Full path `.github\u002Fworkflows\u002Fmain.yml` is auto-stripped to just `main.yml`\n- Inputs max 10 key-value pairs; must match workflow's `on.workflow_dispatch.inputs` definitions\n\n### 6. Manage Users and Permissions\n\n**When to use**: User wants to check collaborators, permissions, or branch protection\n\n**Tool sequence**:\n1. `GITHUB_LIST_REPOSITORY_COLLABORATORS` - List repo collaborators [Required]\n2. `GITHUB_GET_REPOSITORY_PERMISSIONS_FOR_A_USER` - Check specific user's access [Optional]\n3. `GITHUB_GET_BRANCH_PROTECTION` - Inspect branch protection rules [Required]\n4. `GITHUB_UPDATE_BRANCH_PROTECTION` - Update protection settings [Optional]\n5. `GITHUB_ADD_A_REPOSITORY_COLLABORATOR` - Add\u002Fupdate collaborator [Optional]\n\n**Key parameters**:\n- `affiliation`: 'outside', 'direct', or 'all' for collaborator filtering\n- `permission`: Filter by 'pull', 'triage', 'push', 'maintain', 'admin'\n- `branch`: Branch name for protection rules\n- `enforce_admins`: Whether protection applies to admins\n\n**Pitfalls**:\n- `GITHUB_GET_BRANCH_PROTECTION` returns 404 for unprotected branches; treat as no protection rules\n- Determine push ability from `permissions.push` or `role_name`, not display labels\n- `GITHUB_LIST_REPOSITORY_COLLABORATORS` paginates; iterate all pages\n- `GITHUB_GET_REPOSITORY_PERMISSIONS_FOR_A_USER` may be inconclusive for non-collaborators\n\n## Common Patterns\n\n### ID Resolution\n- **Repo name -> owner\u002Frepo**: `GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER`\n- **PR number -> PR details**: `GITHUB_FIND_PULL_REQUESTS` then `GITHUB_GET_A_PULL_REQUEST`\n- **Branch name -> SHA**: `GITHUB_GET_A_BRANCH`\n- **Workflow name -> ID**: `GITHUB_LIST_REPOSITORY_WORKFLOWS`\n\n### Pagination\nAll list endpoints use page-based pagination:\n- `page`: Page number (starts at 1)\n- `per_page`: Results per page (max 100)\n- Iterate until response returns fewer results than `per_page`\n\n### Safety\n- Always verify PR mergeable status before merge\n- Require explicit user confirmation for destructive operations (merge, delete)\n- Check CI status with `GITHUB_LIST_CHECK_RUNS_FOR_A_REF` before merging\n\n## Known Pitfalls\n\n- **Issues vs PRs**: `GITHUB_LIST_REPOSITORY_ISSUES` returns both; check `pull_request` field\n- **Pagination limits**: `per_page` max 100; always iterate pages until empty\n- **Branch creation**: `GITHUB_CREATE_A_REFERENCE` fails with 422 if reference already exists\n- **Merge guards**: Merge can fail due to branch protection, failing checks, or draft status\n- **Code search limits**: Only files \u003C384KB on default branch; max 1000 results\n- **Commit search**: Requires search text keywords alongside qualifiers\n- **Destructive actions**: Repo deletion is irreversible; merge cannot be undone\n- **Silent permission drops**: Labels, assignees, milestones silently dropped without push access\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List repos | `GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER` | `type`, `sort`, `per_page` |\n| Get repo | `GITHUB_GET_A_REPOSITORY` | `owner`, `repo` |\n| Create issue | `GITHUB_CREATE_AN_ISSUE` | `owner`, `repo`, `title`, `body` |\n| List issues | `GITHUB_LIST_REPOSITORY_ISSUES` | `owner`, `repo`, `state` |\n| Find PRs | `GITHUB_FIND_PULL_REQUESTS` | `repo`, `state`, `author` |\n| Create PR | `GITHUB_CREATE_A_PULL_REQUEST` | `owner`, `repo`, `head`, `base`, `title` |\n| Merge PR | `GITHUB_MERGE_A_PULL_REQUEST` | `owner`, `repo`, `pull_number`, `merge_method` |\n| List branches | `GITHUB_LIST_BRANCHES` | `owner`, `repo` |\n| Create branch | `GITHUB_CREATE_A_REFERENCE` | `owner`, `repo`, `ref`, `sha` |\n| Search code | `GITHUB_SEARCH_CODE` | `q` |\n| List commits | `GITHUB_LIST_COMMITS` | `owner`, `repo`, `author`, `since` |\n| Search commits | `GITHUB_SEARCH_COMMITS_BY_AUTHOR` | `q` |\n| List workflows | `GITHUB_LIST_REPOSITORY_WORKFLOWS` | `owner`, `repo` |\n| Trigger workflow | `GITHUB_CREATE_A_WORKFLOW_DISPATCH_EVENT` | `owner`, `repo`, `workflow_id`, `ref` |\n| Check CI | `GITHUB_LIST_CHECK_RUNS_FOR_A_REF` | `owner`, `repo`, ref |\n| List collaborators | `GITHUB_LIST_REPOSITORY_COLLABORATORS` | `owner`, `repo` |\n| Branch protection | `GITHUB_GET_BRANCH_PROTECTION` | `owner`, `repo`, `branch` |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"metadata":53,"description":7},{"risk":35,"source":38,"date_added":54},"2026-02-27","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fgithub-automation",3931,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-14 06:14:46",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add davila7\u002Fclaude-code-templates --skill github-automation",{"tool":71,"command":72},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill github-automation",{"tool":74,"command":75},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill github-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fgithub-automation\u002FSKILL.md",true,[79,85,89],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fstrategies\u002Fmodel-check.md","REFERENCE","参考文档",4022,"https:\u002F\u002Fgithub.com\u002Fasermax\u002Fclaude-plugins\u002Fblob\u002Fmaster\u002Fmahou\u002Fskills\u002Fspike\u002Freferences\u002Fstrategies\u002Fmodel-check.md",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fstrategies\u002Fone-variable.md",729,"https:\u002F\u002Fgithub.com\u002Fasermax\u002Fclaude-plugins\u002Fblob\u002Fmaster\u002Fmahou\u002Fskills\u002Fspike\u002Freferences\u002Fstrategies\u002Fone-variable.md",{"path":90,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fstrategies\u002Fvariants-in-parallel.md",812,"https:\u002F\u002Fgithub.com\u002Fasermax\u002Fclaude-plugins\u002Fblob\u002Fmaster\u002Fmahou\u002Fskills\u002Fspike\u002Freferences\u002Fstrategies\u002Fvariants-in-parallel.md",[94,122,148,180,215,239],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":101,"publishedAt":48},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[100],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121],"scoring","pool","wealthville pool scoring","liquidity","which","for","exit","now","use","when","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":129,"publishedAt":48},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[128],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[130,131,132,133,134,135,136,137,138,139,140,111,44,141,142,143,144,145,146,147],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","todo","work","plan","focus","signals","audit","dependency",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":163,"publishedAt":48},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[154,157,158],{"categoryNo":155,"categoryName":156,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":159,"categoryName":160,"taxonomyType":161,"taxonomyTypeDesc":162},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[164,165,166,167,168,169,170,107,171,172,173,174,175,176,40,110,177,178,111,179],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","access","database","query",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":184,"licenseFileUrl":185,"sourceHtmlUrl":186,"categories":187,"keywords":191,"publishedAt":48},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[188],{"categoryNo":189,"categoryName":190,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[192,193,194,195,196,197,198,199,200,201,202,203,204,205,206,207,208,209,210,211,212,213,107,214],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":184,"licenseFileUrl":219,"sourceHtmlUrl":220,"categories":221,"keywords":226,"publishedAt":48},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[222,225],{"categoryNo":223,"categoryName":224,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":189,"categoryName":190,"taxonomyType":21,"taxonomyTypeDesc":22},[227,228,229,230,231,193,232,202,203,233,234,235,236,107,237,113,238],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":240,"name":241,"nameZh":6,"description":242,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":184,"licenseFileUrl":243,"sourceHtmlUrl":244,"categories":245,"keywords":253,"publishedAt":48},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[246,249,250],{"categoryNo":247,"categoryName":248,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":251,"categoryName":252,"taxonomyType":161,"taxonomyTypeDesc":162},"01JBSEEDCAT000000000000036","内容创作者",[254,255,256,257,258,259,260,261,195,262,205,44,263,47,264,265,266,176,267,111,268,269,270,271,272,119,273],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]