Loading...
Loading...
Found 67 Skills
List all active git worktrees with their status. Use when checking what worktrees exist, their branches, and which has uncommitted changes. Quick overview command.
Travis CI integration. Manage Repositories, Users. Use when the user wants to interact with Travis CI data.
Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.
Administrative workflows for the agent-skills repository. Use when the user wants to contribute a skill, open a pull request, or update an already-installed skill to the latest version. Trigger when users say: "open a PR", "submit my changes", "push this skill", "update my skills", "update the skills repo", or "how do I contribute a skill".
Use when an agent is asked to perform GitHub work in a repository that should follow using-github conventions
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Automate GitHub operations using gh CLI - manage repositories, issues, pull requests, releases, and workflows. Use when working with GitHub, managing repos, creating issues/PRs, or when users mention GitHub operations, gh CLI, or repository management.
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.
Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management
Load all open issues from GitHub and save them as markdown files
Manage git repositories using the worktree pattern for efficient multi-branch development. Use when: (1) Cloning a repository for the first time, (2) Creating a new worktree for a feature branch, (3) Listing existing worktrees, (4) Removing worktrees after work is complete. The worktree pattern clones once and creates lightweight working directories for each branch, avoiding the overhead of multiple full clones.
Reference for GitHub CLI (gh) - READ-ONLY operations only