GitHub CLI Power
A Kiro Power for managing GitHub repositories, issues, pull requests, releases, and Actions workflows using the gh CLI — no MCP server required.
Why
Most GitHub powers rely on an MCP server process. This one takes a simpler approach: it teaches the agent the right gh commands to run directly in your terminal. Zero background processes, zero JSON-RPC overhead, full gh CLI coverage.
Prerequisites
- Install the GitHub CLI
- Authenticate:
gh auth login - Verify:
gh auth status
What's Included
| Path | Description |
|---|---|
plugin.json | Power manifest (Agent Plugins spec) |
power.md | Entry point — overview, routing guide, quick reference |
dev.kiro/steering/gh-cli-patterns.md | General CLI conventions (structured output, non-interactive usage, error handling) |
skills/issues/SKILL.md | Create, search, triage, comment on, and close issues |
skills/pull-requests/SKILL.md | Create, review, merge PRs; stacked PRs; auto-merge |
skills/repos/SKILL.md | Create, clone, fork, configure repos; manage secrets and branch protection |
skills/releases/SKILL.md | Create releases, upload assets, manage drafts and pre-releases |
skills/actions/SKILL.md | Trigger workflows, watch runs, debug failures, manage artifacts and caches |
spec/design.md | Architecture and design decisions |
CHANGELOG.md | Version history |
Installation
In the Kiro IDE: Powers panel → Import power from GitHub → paste https://github.com/chriswessells/github-cli-power.
Or import from a local folder if you've cloned the repo.
Key Design Principles
- Structured output — all commands use
--json+--jqfor reliable parsing - Non-interactive — explicit flags prevent the agent from getting stuck on prompts
gh apiescape hatch — anything the CLI doesn't cover natively is handled via direct API calls- No running processes — pure knowledge power, no servers to manage
License
MIT