New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Git GitHub Ops

by c5inco in c5inco/compose-pokedexer

Handles Pokedexer Git and GitHub workflows: inspect changes, prepare commit messages, manage branches and pushes, and create or update issues and pull requests with safe file-based inputs.

MITAuto-check passedDevelopment

Install Git GitHub Ops

skills CLI
$ npx skills add c5inco/compose-pokedexer --skill git-github-ops -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install c5inco/compose-pokedexer git-github-ops --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/c5inco/compose-pokedexer.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/git-github-ops .claude/skills/git-github-ops && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
git-github-ops
GitHub stars
143
Token cost
~1.3k tokens
SKILL.md length
642 words
Files
4
Skills in repo
3
Repo updated
First seen
Licence
MIT

At a glance

Handles Pokedexer Git and GitHub workflows: inspect changes, prepare commit messages, manage branches and pushes, and create or update issues and pull requests with safe file-based inputs.

  • Works in 7 steps: Run git status --short and inspect git… → Run the relevant targeted tests. → If the change includes .kt or .kts… → …
  • Tasks that involve Commit messages
  • SKILL.md covers Operating Rules, Commit Message Contract, Commit Workflow and Branch and Push Workflow, plus 4 more sections
  • Calls git and gh

What it does

Git GitHub Ops is an agent skill from c5inco/compose-pokedexer. Handles Pokedexer Git and GitHub workflows: inspect changes, prepare commit messages, manage branches and pushes, and create or update issues and pull requests with safe file-based inputs. Use for any git or gh operation.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `templates/issue-body.md` and `templates/pr-description.md`).

It sits in Development, covering Commit messages, Git workflow and Pull requests. It works with Git, GitHub, GitHub Actions and Jetpack Compose. The repository describes itself as: Pokedex app written in Compose, powered by PokeAPI.co. The licence is MIT.

When your agent uses it

  • Tasks that involve Commit messages
  • Tasks that involve Git workflow
  • Tasks that involve Pull requests

Example prompts

  • “Use the git-github-ops skill to handle Pokedexer Git and GitHub workflows: inspect changes, prepare commit messages, manage branches and pushes, and…”
  • “/git-github-ops”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Run git status --short and inspect git diff.
  2. Run the relevant targeted tests.
  3. If the change includes .kt or .kts files, run ./gradlew ktfmtFormat, then inspect the diff again.
  4. Stage only files in scope.
  5. Inspect git diff --staged.
  6. Write the message to a temporary file, optionally starting from templates/commit-message.txt.
  7. After explicit commit approval, run git commit -F /tmp/pokedexer-commit-message.txt.

What it can do on your machine

Read from SKILL.md and the folder at commit d2f8992. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Git GitHub Ops loads about 1.3k tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 642 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~59
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from c5inco/compose-pokedexer at commit d2f8992, republished under its MIT licence (© c5inco). 642 words, ~1,310 tokens.

Download SKILL.mdSave it as .claude/skills/git-github-ops/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
git-github-ops
description
Handles Pokedexer Git and GitHub workflows: inspect changes, prepare commit messages, manage branches and pushes, and create or update issues and pull requests with safe file-based inputs. Use for any git or gh operation.

Git and GitHub Operations

Handle Git and GitHub work from the real repository state while respecting the approval gates in AGENTS.md.

Operating Rules

  • Read AGENTS.md and docs/CONVENTIONS.md before mutating Git or GitHub state.
  • Read-only inspection is allowed without approval.
  • Obtain explicit user approval before persistently changing repository history, branches, worktrees, remotes, issues, or pull requests. Approval for one operation does not imply approval for later operations.
  • Never discard or rewrite work that the user or another agent may own.
  • Use gh for GitHub operations and explicit, non-interactive flags.
  • Keep each shell command focused on one purpose.
  • Put multiline commit, issue, PR, and comment text in a file; pass the file to git or gh instead of embedding it in a shell command.
  • Keep labels in GitHub metadata. Never add a Labels section to an issue body.

Commit Message Contract

Derive every claim from git diff --staged.

  • Describe the concrete change and why it matters.
  • Do not invent issue IDs, names, emails, or other metadata.
  • Do not use typed Conventional Commit prefixes (feat:, fix:, docs:, chore:, refactor:, or scoped variants). If one area is the clear focus, a bare area label is acceptable: search: avoid stale results.
  • Use an imperative subject no longer than 72 characters.
  • Add a blank line before the body and wrap body lines at 72 characters.

Use this shape:

text
<imperative subject, <= 72 characters>

- <specific diff-derived change>
- <specific diff-derived change>
- <validation performed>

Commit Workflow

  1. Run git status --short and inspect git diff.
  2. Run the relevant targeted tests.
  3. If the change includes .kt or .kts files, run ./gradlew ktfmtFormat, then inspect the diff again.
  4. Stage only files in scope.
  5. Inspect git diff --staged.
  6. Write the message to a temporary file, optionally starting from templates/commit-message.txt.
  7. After explicit commit approval, run git commit -F /tmp/pokedexer-commit-message.txt.

Do not amend, reset, rebase, or otherwise rewrite a commit unless the user explicitly approves that exact operation.

Branch and Push Workflow

  • Use descriptive branch names such as fix/search-race or feat/item-details.
  • Before creating or switching branches, inspect the current branch, status, and worktree list.
  • Never pull, merge, or rebase merely to make a branch current. Report the state and ask which update strategy the user wants.
  • Before every push or PR, run ./gradlew check and confirm it passes. If it fails, stop unless every pre-existing check failure exception requirement in AGENTS.md is documented and satisfied.
  • Push the explicit branch name; use git push --set-upstream origin <branch> for its first push.
  • Never push directly to the default branch unless the user explicitly requests that exact action.

Every branch creation or deletion, pull, merge, rebase, push, and worktree mutation requires explicit approval under AGENTS.md.

Show full SKILL.md (211 more words)Show less

Pull Request Workflow

Use a focused, review-friendly title:

text
<area>: <what changed and why it matters>

Keep it near 72 characters and describe the outcome rather than the process.

Write the PR body to a temporary Markdown file, optionally starting from templates/pr-description.md, then use:

bash
gh pr create --title "<title>" --body-file /tmp/pokedexer-pr-body.md --base <default-branch> --head <branch>

Opening, editing, closing, or merging a PR requires explicit user approval. A request to implement a change does not implicitly authorize opening a PR.

For PR comments and review replies, also use file inputs:

bash
gh pr comment <pr-number> --body-file /tmp/pokedexer-pr-comment.md

Issue Workflow

Before selecting labels, inspect the repository's current labels with gh label list. Create issue text from templates/issue-body.md, then use a file input:

bash
gh issue create --title "<title>" --body-file /tmp/pokedexer-issue-body.md --label "<validated-label>"

Creating, editing, labeling, commenting on, closing, or reopening an issue requires explicit user approval.

Safety Checklist

Before an approval-gated Git or GitHub mutation:

  • Confirm the user approved the exact operation.
  • Confirm the active checkout, branch, and worktree are the intended targets.
  • Confirm unrelated changes are excluded and preserved.
  • Confirm TDD evidence exists for behavior changes.
  • Before commits, confirm formatting and targeted tests pass.
  • Before pushes and PRs, confirm ./gradlew check passes or document how every AGENTS.md pre-existing failure exception requirement is satisfied.

Handoff

Report only operations actually completed, including:

  • branch and commit subject, if created;
  • push destination, if pushed;
  • issue or PR link, if created or updated;
  • tests and checks run;
  • approvals or unresolved failures still pending.

© c5inco, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files in .agents/skills/git-github-ops of c5inco/compose-pokedexer.

  • SKILL.md
  • templates/commit-message.txt
  • templates/issue-body.md
  • templates/pr-description.md

Open the folder on GitHubat commit d2f8992

Compare with similar skills

Git GitHub Ops next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Git GitHub Ops compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Git GitHub Ops this skillc5inco/compose-pokedexer143—~1.3kAutomated safety check: PassMIT
Stewardyschimke/compose-ai-tools117—~2kAutomated safety check: PassApache-2.0
React Router Pull Request Creatorremix-run/react-router57k—~2.5kAutomated safety check: PassMIT
Draft Pull Request Creatorwordpress-mobile/WordPress-Android3.2k—~881Automated safety check: NotesGPL-2.0
ZCF Release AutomationUfoMiao/zcf6.1k—~3.4kAutomated safety check: PassMIT
Release Changelogsk2andy/candy-browser488—~593Automated safety check: PassMPL-2.0

Similar skills

  • Steward

    yschimke/compose-ai-tools

    Drive a pull request on this repository to green — which fast checks to run before pushing, how to read a red check, and what to do about a review comment.

    117 GitHub stars~2k tokensUpdated today
    DevelopmentAuto-check passed

  • React Router Pull Request Creator

    remix-run/react-router

    Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.

    57k GitHub stars~2.5k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Draft Pull Request Creator

    wordpress-mobile/WordPress-Android

    Commits and pushes current changes, writes a pull request title and body from the branch history and template, and opens a draft PR on GitHub after you approve it.

    3.2k GitHub stars~881 tokensUpdated today
    DevelopmentAuto-check: notes

  • ZCF Release Automation

    UfoMiao/zcf

    Automates a version release with changesets: analyzes code changes, writes a bilingual CHANGELOG, bumps the version and commits through a release branch and pull request.

    6.1k GitHub stars~3.4k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Release Changelog

    sk2andy/candy-browser

    Create or update Candy Browser's English, image-rich, versioned release notes for the in-app What's New presentation and the matching GitHub release.

    488 GitHub stars~593 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Kt Search Release

    jillesvangurp/kt-search

    A skill your agent uses when the user wants to cut, publish, tag, or create a GitHub release for kt-search, especially when the task includes version bumping, validating that commits are pushed…

    155 GitHub stars~1.2k tokensUpdated 3 mo ago
    DevelopmentAuto-check passed

More from c5inco/compose-pokedexer

  • Xcodebuildmcp CLI

    c5inco/compose-pokedexer

    Official skill for the XcodeBuildMCP CLI. An agent skill from c5inco/compose-pokedexer.

    143 GitHub stars~415 tokensUpdated 5 days ago
    Auto-check passed

  • Using Git Worktree

    c5inco/compose-pokedexer

    Creates and manages isolated Git worktrees with safe directory selection, explicit approval, clean-baseline verification, and Gradle-specific safeguards.

    143 GitHub stars~1.4k tokensUpdated 5 days ago
    Auto-check passed

Works with

Categories

Questions about Git GitHub Ops

What does Git GitHub Ops do?

Handles Pokedexer Git and GitHub workflows: inspect changes, prepare commit messages, manage branches and pushes, and create or update issues and pull requests with safe file-based inputs. Git GitHub Ops is an agent skill from c5inco/compose-pokedexer. Handles Pokedexer Git and GitHub workflows: inspect changes, prepare commit messages, manage branches and pushes, and create or update issues and pull requests with safe file-based inputs.

When should I use Git GitHub Ops?

Git GitHub Ops fits situations like: tasks that involve Commit messages; tasks that involve Git workflow; tasks that involve Pull requests.

How do I install Git GitHub Ops in Claude Code?

Run `npx skills add c5inco/compose-pokedexer --skill git-github-ops -a claude-code`. Or copy the skill folder (.agents/skills/git-github-ops in c5inco/compose-pokedexer) into .claude/skills/git-github-ops in your project. Claude Code loads it when a task matches its description.

How do I install Git GitHub Ops in Codex?

Run `npx skills add c5inco/compose-pokedexer --skill git-github-ops -a codex`. Or copy the skill folder (.agents/skills/git-github-ops in c5inco/compose-pokedexer) into .agents/skills/git-github-ops in your project. Codex loads it when a task matches its description.

Can I use Git GitHub Ops in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add c5inco/compose-pokedexer --skill git-github-ops -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/git-github-ops, .gemini/skills/git-github-ops, .github/skills/git-github-ops and .opencode/skills/git-github-ops in your project.

What does Git GitHub Ops need to run?

Going by SKILL.md and its folder, Git GitHub Ops needs the command-line tools its instructions call (git and gh).

Does Git GitHub Ops access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Git GitHub Ops safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Git GitHub Ops use?

Git GitHub Ops is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Git GitHub Ops use?

About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Git GitHub Ops?

Skills that share tags, products or a category with Git GitHub Ops: Steward (yschimke/compose-ai-tools, 117 stars), React Router Pull Request Creator (remix-run/react-router, 57k stars), Draft Pull Request Creator (wordpress-mobile/WordPress-Android, 3.2k stars) and ZCF Release Automation (UfoMiao/zcf, 6.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Git GitHub Ops?

c5inco (a GitHub user) maintains it in c5inco/compose-pokedexer, which has 143 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 3, 2026.

Source: c5inco/compose-pokedexer on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.