📦 deps(thirdparty): update snapshots
This commit is contained in:
ci[bot]
+1
-1
@@ -1,6 +1,6 @@
|
||||
{
|
||||
"name": "agentic-bundle-aas-automation-builder",
|
||||
"version": "14.3.1",
|
||||
"version": "14.6.0",
|
||||
"description": "Editorial \"AAS Automation Builder\" bundle for Claude Code from Agentic Awesome Skills.",
|
||||
"author": {
|
||||
"name": "sickn33 and contributors",
|
||||
|
||||
+1
-1
@@ -1,6 +1,6 @@
|
||||
{
|
||||
"name": "aasb-aas-automation-builder",
|
||||
"version": "14.3.1",
|
||||
"version": "14.6.0",
|
||||
"description": "Install the \"AAS Automation Builder\" workflow plugin from Agentic Awesome Skills.",
|
||||
"author": {
|
||||
"name": "sickn33 and contributors",
|
||||
|
||||
+56
-198
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: github-automation
|
||||
description: "Automate GitHub repositories, issues, pull requests, branches, CI/CD, and permissions via Rube MCP (Composio). Manage code workflows, review PRs, search code, and handle deployments programmatically."
|
||||
description: "Operate GitHub issues, pull requests, branches, checks, workflows, and permissions through Rube MCP. Use when GitHub work must be queried or changed programmatically with repository-policy safeguards."
|
||||
risk: critical
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
@@ -8,228 +8,86 @@ date_added: "2026-02-27"
|
||||
|
||||
# GitHub Automation via Rube MCP
|
||||
|
||||
Automate GitHub repository management, issue tracking, pull request workflows, branch operations, and CI/CD through Composio's GitHub toolkit.
|
||||
Use Composio's GitHub toolkit through Rube MCP while preserving repository policy, exact revision identity, and branch protection.
|
||||
|
||||
## Prerequisites
|
||||
## When to Use
|
||||
|
||||
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
|
||||
- Active GitHub connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `github`
|
||||
- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
|
||||
Use for programmatic GitHub issue, pull-request, branch, Actions, deployment, collaborator, or protection tasks when Rube MCP is available. Prefer the native `gh` workflow or a repository-specific maintainer command when local repository policy requires it.
|
||||
|
||||
## Setup
|
||||
|
||||
**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
|
||||
1. Confirm `RUBE_SEARCH_TOOLS` is available.
|
||||
2. Search for the current GitHub tool schemas before composing calls.
|
||||
3. Use `RUBE_MANAGE_CONNECTIONS` with toolkit `github` and complete OAuth only if the connection is not active.
|
||||
4. Resolve the exact `owner/repo`; do not rely on a similarly named repository.
|
||||
|
||||
1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
|
||||
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `github`
|
||||
3. If connection is not ACTIVE, follow the returned auth link to complete GitHub OAuth
|
||||
4. Confirm connection status shows ACTIVE before running any workflows
|
||||
Never request, print, or persist GitHub credentials in prompts or artifacts.
|
||||
|
||||
## Core Workflows
|
||||
## Repository Policy Gate
|
||||
|
||||
### 1. Create and Manage Issues
|
||||
Before mutation, read `AGENTS.md`, contribution and maintainer docs, then inspect the default branch and effective protection. Repository-native commands and required checks take precedence over generic Rube operations.
|
||||
|
||||
**When to use**: User wants to create, list, or manage GitHub issues
|
||||
If a repository provides a guarded merge or release command, use it instead of the generic merge tool. In `agentic-awesome-skills`, use `antigravity-maintainer-batch-release` and `npm run merge:batch` so exact-SHA review, fresh check-suite binding, and protected `main` are enforced.
|
||||
|
||||
**Tool sequence**:
|
||||
1. `GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER` - Find target repo if unknown [Prerequisite]
|
||||
2. `GITHUB_LIST_REPOSITORY_ISSUES` - List existing issues (includes PRs) [Required]
|
||||
3. `GITHUB_CREATE_AN_ISSUE` - Create a new issue [Required]
|
||||
4. `GITHUB_CREATE_AN_ISSUE_COMMENT` - Add comments to an issue [Optional]
|
||||
5. `GITHUB_SEARCH_ISSUES_AND_PULL_REQUESTS` - Search across repos by keyword [Optional]
|
||||
## Workflows
|
||||
|
||||
**Key parameters**:
|
||||
- `owner`: Repository owner (username or org), case-insensitive
|
||||
- `repo`: Repository name without .git extension
|
||||
- `title`: Issue title (required for creation)
|
||||
- `body`: Issue description (supports Markdown)
|
||||
- `labels`: Array of label names
|
||||
- `assignees`: Array of GitHub usernames
|
||||
- `state`: 'open', 'closed', or 'all' for filtering
|
||||
### Issues
|
||||
|
||||
**Pitfalls**:
|
||||
- `GITHUB_LIST_REPOSITORY_ISSUES` returns both issues AND pull requests; check `pull_request` field to distinguish
|
||||
- Only users with push access can set assignees, labels, and milestones; they are silently dropped otherwise
|
||||
- Pagination: `per_page` max 100; iterate pages until empty
|
||||
1. List or search existing issues before creating a duplicate.
|
||||
2. Distinguish issues from pull requests in mixed results.
|
||||
3. Read the current item, comments, labels, and linked PRs before changing state.
|
||||
4. Create, comment, label, assign, or close only within the user's requested scope.
|
||||
5. Re-read the item and verify the resulting state.
|
||||
|
||||
### 2. Manage Pull Requests
|
||||
Paginate until the requested result set is complete. Treat silent omission of labels or assignees as a permissions failure, not success.
|
||||
|
||||
**When to use**: User wants to create, review, or merge pull requests
|
||||
### Pull requests
|
||||
|
||||
**Tool sequence**:
|
||||
1. `GITHUB_FIND_PULL_REQUESTS` - Search and filter PRs [Required]
|
||||
2. `GITHUB_GET_A_PULL_REQUEST` - Get detailed PR info including mergeable status [Required]
|
||||
3. `GITHUB_LIST_PULL_REQUESTS_FILES` - Review changed files [Optional]
|
||||
4. `GITHUB_CREATE_A_PULL_REQUEST` - Create a new PR [Required]
|
||||
5. `GITHUB_CREATE_AN_ISSUE_COMMENT` - Post review comments [Optional]
|
||||
6. `GITHUB_LIST_CHECK_RUNS_FOR_A_REF` - Verify CI status before merge [Optional]
|
||||
7. `GITHUB_MERGE_A_PULL_REQUEST` - Merge after explicit user approval [Required]
|
||||
1. Resolve the PR and capture its number, base, full head SHA, draft state, author, fork identity, and mergeability.
|
||||
2. Inspect changed files, reviews, conversations, and required check runs.
|
||||
3. Bind every review or approval decision to the current full head SHA.
|
||||
4. Create or update the PR body truthfully; never mark pending tests or reviews as completed.
|
||||
5. Immediately before merge, re-read base/head identity, branch protection, mergeability, required checks, and repository policy.
|
||||
6. Use the repository's guarded merge path. Call a generic merge tool only when policy permits it and the user authorized the merge.
|
||||
7. Verify the PR reports `MERGED` and confirm the target branch contains the intended commit.
|
||||
|
||||
**Key parameters**:
|
||||
- `head`: Source branch with changes (must exist; for cross-repo: 'username:branch')
|
||||
- `base`: Target branch to merge into (e.g., 'main')
|
||||
- `title`: PR title (required unless `issue` number provided)
|
||||
- `merge_method`: 'merge', 'squash', or 'rebase'
|
||||
- `state`: 'open', 'closed', or 'all'
|
||||
Do not treat a successful API call that enables auto-merge or queues work as an immediate merge.
|
||||
|
||||
**Pitfalls**:
|
||||
- `GITHUB_CREATE_A_PULL_REQUEST` fails with 422 if base/head are invalid, identical, or already merged
|
||||
- `GITHUB_MERGE_A_PULL_REQUEST` can be rejected if PR is draft, closed, or branch protection applies
|
||||
- Always verify mergeable status with `GITHUB_GET_A_PULL_REQUEST` immediately before merging
|
||||
- Require explicit user confirmation before calling MERGE
|
||||
### Branches and references
|
||||
|
||||
### 3. Manage Repositories and Branches
|
||||
1. Resolve the source commit SHA and target ref explicitly.
|
||||
2. Create topic branches rather than updating protected/default branches directly.
|
||||
3. Reject non-fast-forward or force updates unless the user explicitly authorizes them and repository policy permits them.
|
||||
4. Confirm the remote ref after mutation.
|
||||
|
||||
**When to use**: User wants to create repos, manage branches, or update repo settings
|
||||
Deletion, force-push, default-branch changes, and protection changes are destructive or high-impact actions requiring explicit authorization.
|
||||
|
||||
**Tool sequence**:
|
||||
1. `GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER` - List user's repos [Required]
|
||||
2. `GITHUB_GET_A_REPOSITORY` - Get detailed repo info [Optional]
|
||||
3. `GITHUB_CREATE_A_REPOSITORY_FOR_THE_AUTHENTICATED_USER` - Create personal repo [Required]
|
||||
4. `GITHUB_CREATE_AN_ORGANIZATION_REPOSITORY` - Create org repo [Alternative]
|
||||
5. `GITHUB_LIST_BRANCHES` - List branches [Required]
|
||||
6. `GITHUB_CREATE_A_REFERENCE` - Create new branch from SHA [Required]
|
||||
7. `GITHUB_UPDATE_A_REPOSITORY` - Update repo settings [Optional]
|
||||
### Actions and deployments
|
||||
|
||||
**Key parameters**:
|
||||
- `name`: Repository name
|
||||
- `private`: Boolean for visibility
|
||||
- `ref`: Full reference path (e.g., 'refs/heads/new-branch')
|
||||
- `sha`: Commit SHA to point the new reference to
|
||||
- `default_branch`: Default branch name
|
||||
1. Resolve the workflow by trusted ID or path and confirm `workflow_dispatch` support before dispatch.
|
||||
2. Bind run inspection to the intended event, ref, and head SHA.
|
||||
3. Distinguish `queued`, `in_progress`, `action_required`, `completed`, and `skipped` states.
|
||||
4. Read failed job logs before proposing source changes.
|
||||
5. Wait for terminal success and verify the deployed or published surface separately.
|
||||
|
||||
**Pitfalls**:
|
||||
- `GITHUB_CREATE_A_REFERENCE` only creates NEW references; use `GITHUB_UPDATE_A_REFERENCE` for existing ones
|
||||
- `ref` must start with 'refs/' and contain at least two slashes
|
||||
- `GITHUB_LIST_BRANCHES` paginates via `page`/`per_page`; iterate until empty page
|
||||
- `GITHUB_DELETE_A_REPOSITORY` is permanent and irreversible; requires admin privileges
|
||||
Do not approve fork workflow runs by raw run ID when the repository provides a guarded approval command.
|
||||
|
||||
### 4. Search Code and Commits
|
||||
### Permissions and protection
|
||||
|
||||
**When to use**: User wants to find code, files, or commits across repositories
|
||||
1. Read collaborators, role, branch protection, and applicable rulesets before proposing changes.
|
||||
2. Treat a 404 protection response as “not configured” only after confirming repository and branch identity.
|
||||
3. Show the exact before/after policy and impact before any protection or permission mutation.
|
||||
4. Re-read effective state after the change.
|
||||
|
||||
**Tool sequence**:
|
||||
1. `GITHUB_SEARCH_CODE` - Search file contents and paths [Required]
|
||||
2. `GITHUB_SEARCH_CODE_ALL_PAGES` - Multi-page code search [Alternative]
|
||||
3. `GITHUB_SEARCH_COMMITS_BY_AUTHOR` - Search commits by author/date/org [Required]
|
||||
4. `GITHUB_LIST_COMMITS` - List commits for a specific repo [Alternative]
|
||||
5. `GITHUB_GET_A_COMMIT` - Get detailed commit info [Optional]
|
||||
6. `GITHUB_GET_REPOSITORY_CONTENT` - Get file content [Optional]
|
||||
## Failure Rules
|
||||
|
||||
**Key parameters**:
|
||||
- `q`: Search query with qualifiers (`language:python`, `repo:owner/repo`, `extension:js`)
|
||||
- `owner`/`repo`: For repo-specific commit listing
|
||||
- `author`: Filter by commit author
|
||||
- `since`/`until`: ISO 8601 date range for commits
|
||||
|
||||
**Pitfalls**:
|
||||
- Code search only indexes files under 384KB on default branch
|
||||
- Maximum 1000 results returned from code search
|
||||
- `GITHUB_SEARCH_COMMITS_BY_AUTHOR` requires keywords in addition to qualifiers; qualifier-only queries are not allowed
|
||||
- `GITHUB_LIST_COMMITS` returns 409 on empty repos
|
||||
|
||||
### 5. Manage CI/CD and Deployments
|
||||
|
||||
**When to use**: User wants to view workflows, check CI status, or manage deployments
|
||||
|
||||
**Tool sequence**:
|
||||
1. `GITHUB_LIST_REPOSITORY_WORKFLOWS` - List GitHub Actions workflows [Required]
|
||||
2. `GITHUB_GET_A_WORKFLOW` - Get workflow details by ID or filename [Optional]
|
||||
3. `GITHUB_CREATE_A_WORKFLOW_DISPATCH_EVENT` - Manually trigger a workflow [Required]
|
||||
4. `GITHUB_LIST_CHECK_RUNS_FOR_A_REF` - Check CI status for a commit/branch [Required]
|
||||
5. `GITHUB_LIST_DEPLOYMENTS` - List deployments [Optional]
|
||||
6. `GITHUB_GET_A_DEPLOYMENT_STATUS` - Get deployment status [Optional]
|
||||
|
||||
**Key parameters**:
|
||||
- `workflow_id`: Numeric ID or filename (e.g., 'ci.yml')
|
||||
- `ref`: Git reference (branch/tag) for workflow dispatch
|
||||
- `inputs`: JSON string of workflow inputs matching `on.workflow_dispatch.inputs`
|
||||
- `environment`: Filter deployments by environment name
|
||||
|
||||
**Pitfalls**:
|
||||
- `GITHUB_CREATE_A_WORKFLOW_DISPATCH_EVENT` requires the workflow to have `workflow_dispatch` trigger configured
|
||||
- Full path `.github/workflows/main.yml` is auto-stripped to just `main.yml`
|
||||
- Inputs max 10 key-value pairs; must match workflow's `on.workflow_dispatch.inputs` definitions
|
||||
|
||||
### 6. Manage Users and Permissions
|
||||
|
||||
**When to use**: User wants to check collaborators, permissions, or branch protection
|
||||
|
||||
**Tool sequence**:
|
||||
1. `GITHUB_LIST_REPOSITORY_COLLABORATORS` - List repo collaborators [Required]
|
||||
2. `GITHUB_GET_REPOSITORY_PERMISSIONS_FOR_A_USER` - Check specific user's access [Optional]
|
||||
3. `GITHUB_GET_BRANCH_PROTECTION` - Inspect branch protection rules [Required]
|
||||
4. `GITHUB_UPDATE_BRANCH_PROTECTION` - Update protection settings [Optional]
|
||||
5. `GITHUB_ADD_A_REPOSITORY_COLLABORATOR` - Add/update collaborator [Optional]
|
||||
|
||||
**Key parameters**:
|
||||
- `affiliation`: 'outside', 'direct', or 'all' for collaborator filtering
|
||||
- `permission`: Filter by 'pull', 'triage', 'push', 'maintain', 'admin'
|
||||
- `branch`: Branch name for protection rules
|
||||
- `enforce_admins`: Whether protection applies to admins
|
||||
|
||||
**Pitfalls**:
|
||||
- `GITHUB_GET_BRANCH_PROTECTION` returns 404 for unprotected branches; treat as no protection rules
|
||||
- Determine push ability from `permissions.push` or `role_name`, not display labels
|
||||
- `GITHUB_LIST_REPOSITORY_COLLABORATORS` paginates; iterate all pages
|
||||
- `GITHUB_GET_REPOSITORY_PERMISSIONS_FOR_A_USER` may be inconclusive for non-collaborators
|
||||
|
||||
## Common Patterns
|
||||
|
||||
### ID Resolution
|
||||
- **Repo name -> owner/repo**: `GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER`
|
||||
- **PR number -> PR details**: `GITHUB_FIND_PULL_REQUESTS` then `GITHUB_GET_A_PULL_REQUEST`
|
||||
- **Branch name -> SHA**: `GITHUB_GET_A_BRANCH`
|
||||
- **Workflow name -> ID**: `GITHUB_LIST_REPOSITORY_WORKFLOWS`
|
||||
|
||||
### Pagination
|
||||
All list endpoints use page-based pagination:
|
||||
- `page`: Page number (starts at 1)
|
||||
- `per_page`: Results per page (max 100)
|
||||
- Iterate until response returns fewer results than `per_page`
|
||||
|
||||
### Safety
|
||||
- Always verify PR mergeable status before merge
|
||||
- Require explicit user confirmation for destructive operations (merge, delete)
|
||||
- Check CI status with `GITHUB_LIST_CHECK_RUNS_FOR_A_REF` before merging
|
||||
|
||||
## Known Pitfalls
|
||||
|
||||
- **Issues vs PRs**: `GITHUB_LIST_REPOSITORY_ISSUES` returns both; check `pull_request` field
|
||||
- **Pagination limits**: `per_page` max 100; always iterate pages until empty
|
||||
- **Branch creation**: `GITHUB_CREATE_A_REFERENCE` fails with 422 if reference already exists
|
||||
- **Merge guards**: Merge can fail due to branch protection, failing checks, or draft status
|
||||
- **Code search limits**: Only files <384KB on default branch; max 1000 results
|
||||
- **Commit search**: Requires search text keywords alongside qualifiers
|
||||
- **Destructive actions**: Repo deletion is irreversible; merge cannot be undone
|
||||
- **Silent permission drops**: Labels, assignees, milestones silently dropped without push access
|
||||
|
||||
## Quick Reference
|
||||
|
||||
| Task | Tool Slug | Key Params |
|
||||
|------|-----------|------------|
|
||||
| List repos | `GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER` | `type`, `sort`, `per_page` |
|
||||
| Get repo | `GITHUB_GET_A_REPOSITORY` | `owner`, `repo` |
|
||||
| Create issue | `GITHUB_CREATE_AN_ISSUE` | `owner`, `repo`, `title`, `body` |
|
||||
| List issues | `GITHUB_LIST_REPOSITORY_ISSUES` | `owner`, `repo`, `state` |
|
||||
| Find PRs | `GITHUB_FIND_PULL_REQUESTS` | `repo`, `state`, `author` |
|
||||
| Create PR | `GITHUB_CREATE_A_PULL_REQUEST` | `owner`, `repo`, `head`, `base`, `title` |
|
||||
| Merge PR | `GITHUB_MERGE_A_PULL_REQUEST` | `owner`, `repo`, `pull_number`, `merge_method` |
|
||||
| List branches | `GITHUB_LIST_BRANCHES` | `owner`, `repo` |
|
||||
| Create branch | `GITHUB_CREATE_A_REFERENCE` | `owner`, `repo`, `ref`, `sha` |
|
||||
| Search code | `GITHUB_SEARCH_CODE` | `q` |
|
||||
| List commits | `GITHUB_LIST_COMMITS` | `owner`, `repo`, `author`, `since` |
|
||||
| Search commits | `GITHUB_SEARCH_COMMITS_BY_AUTHOR` | `q` |
|
||||
| List workflows | `GITHUB_LIST_REPOSITORY_WORKFLOWS` | `owner`, `repo` |
|
||||
| Trigger workflow | `GITHUB_CREATE_A_WORKFLOW_DISPATCH_EVENT` | `owner`, `repo`, `workflow_id`, `ref` |
|
||||
| Check CI | `GITHUB_LIST_CHECK_RUNS_FOR_A_REF` | `owner`, `repo`, ref |
|
||||
| List collaborators | `GITHUB_LIST_REPOSITORY_COLLABORATORS` | `owner`, `repo` |
|
||||
| Branch protection | `GITHUB_GET_BRANCH_PROTECTION` | `owner`, `repo`, `branch` |
|
||||
|
||||
## When to Use
|
||||
This skill is applicable to execute the workflow or actions described in the overview.
|
||||
- Re-resolve tool schemas when Rube reports missing or changed parameters.
|
||||
- Stop on repository ambiguity, stale head/base SHA, missing permissions, incomplete pagination, or inconclusive protection state.
|
||||
- Never bypass required checks, reviews, merge queues, maintainer commands, or server-side branch protection.
|
||||
- Do not claim a merge, workflow, deployment, or permission change succeeded without reading the resulting remote state.
|
||||
|
||||
## Limitations
|
||||
- Use this skill only when the task clearly matches the scope described above.
|
||||
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
|
||||
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
|
||||
|
||||
- Available Rube tool names and schemas can change; discover them at runtime.
|
||||
- GitHub permissions, organization policy, and external checks can block otherwise valid operations.
|
||||
- This skill does not authorize repository deletion, force pushes, protection changes, merges, deployments, or releases beyond explicit user intent.
|
||||
|
||||
Reference in New Issue
Block a user