plugins-copilot/git-cli/skills/git-cli/SKILL.md
Interact with GitHub and Gitea issue trackers and CI systems. List and show issues, file bugs, comment on issues or PRs, list and show pull requests, and fetch CI run logs — all from any repo context without leaving the session.
npx skillsauth add st0nefish/claude-toolkit git-cliInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use ${COPILOT_PLUGIN_ROOT}/scripts/git-cli to interact with the issue tracker and CI
system for the current repository. Platform (GitHub or Gitea) is auto-detected from the
git remote — no configuration needed.
# List open issues (returns normalized JSON array)
${COPILOT_PLUGIN_ROOT}/scripts/git-cli issue list [--limit N] [--state open|closed|all] [--label LABEL] [--assignee USER]
# Show a single issue with full body and comments
${COPILOT_PLUGIN_ROOT}/scripts/git-cli issue show <number>
# Create an issue (pipe body to --body via heredoc)
${COPILOT_PLUGIN_ROOT}/scripts/git-cli issue create --title "Title" --body [--label bug] <<'EOF'
## Problem
...
EOF
# Add a comment (heredoc for multi-line, printf for short)
${COPILOT_PLUGIN_ROOT}/scripts/git-cli issue comment <number> --body <<'EOF'
Progress update...
EOF
printf 'LGTM' | ${COPILOT_PLUGIN_ROOT}/scripts/git-cli issue comment <number> --body
# Close or reopen
${COPILOT_PLUGIN_ROOT}/scripts/git-cli issue close <number>
${COPILOT_PLUGIN_ROOT}/scripts/git-cli issue reopen <number>
# List PRs
${COPILOT_PLUGIN_ROOT}/scripts/git-cli pr list [--state open|closed|merged|all] [--limit N]
# Show a single PR with details
${COPILOT_PLUGIN_ROOT}/scripts/git-cli pr show <number>
# Create a PR (auto-assigns to current user)
${COPILOT_PLUGIN_ROOT}/scripts/git-cli pr create --title "Title" --head branch --base main --body <<'EOF'
## Summary
...
## Test plan
...
EOF
# Comment on a PR
${COPILOT_PLUGIN_ROOT}/scripts/git-cli pr comment <number> --body <<'EOF'
Review follow-up...
EOF
# Merge or close
${COPILOT_PLUGIN_ROOT}/scripts/git-cli pr merge <number> [--squash | --rebase]
${COPILOT_PLUGIN_ROOT}/scripts/git-cli pr close <number>
# List recent runs (JSON with id, status, workflow, branch, event, started_at)
${COPILOT_PLUGIN_ROOT}/scripts/git-cli run list [--limit N] [--status failure|success|pending] [--branch BRANCH]
# Show details of a specific run
${COPILOT_PLUGIN_ROOT}/scripts/git-cli run show <run-id>
# Fetch logs (--failed-only shows only failing steps on GitHub)
${COPILOT_PLUGIN_ROOT}/scripts/git-cli run logs <run-id>
${COPILOT_PLUGIN_ROOT}/scripts/git-cli run logs <run-id> --failed-only
${COPILOT_PLUGIN_ROOT}/scripts/git-cli repo default-branch # e.g. "main" or "master"
${COPILOT_PLUGIN_ROOT}/scripts/git-cli repo info # name, description, stars, etc.
${COPILOT_PLUGIN_ROOT}/scripts/git-cli user whoami # {"login": "username"}
All commands return JSON. Issue and PR objects use a normalized schema:
{
"number": 42,
"title": "...",
"body": "...",
"state": "open",
"author": "username",
"labels": ["bug", "high-priority"],
"milestone": null,
"assignees": ["username"],
"created_at": "2026-01-01T00:00:00Z",
"updated_at": "2026-01-01T00:00:00Z",
"url": "https://..."
}
Pipe the body to --body via a heredoc. No temp file, no cleanup:
${COPILOT_PLUGIN_ROOT}/scripts/git-cli issue create --title "Bug: ..." --label bug --body <<'EOF'
## Problem
...
## Steps to reproduce
...
EOF
--body-file FILE remains available when the body is already on disk, and
--body-file - is equivalent to --body (reads stdin). There is no
--body TEXT form — stdin handles every size from one-liners to full PR
descriptions.
development
Start work from your description — explore the codebase and plan
data-ai
Multi-phase, multi-agent feature workflow: spec → plan → refine → divide → execute → review. Invoke when the user escalates a session-start/session-issue flow to orchestration, or asks to run a non-trivial feature (multiple files, design ambiguity, cross-cutting concerns, correctness-critical paths) through the full multi-agent workflow. For small fixes, prefer session-start.
tools
Browse open issues, pick one, and start work on it
tools
Review, clean up, and open a PR to finalize the work