Agent skill

GitHub Ops

by affaan-m in affaan-m/ECC

GitHub操作、自動化、APIインテグレーション、およびCI/CDワークフロー. An agent skill from affaan-m/ECC.

MITAuto-check passedDevOps & Cloud

Install GitHub Ops

skills CLI
$ npx skills add affaan-m/ECC --skill github-ops -a claude-code

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

GitHub CLI
$ gh skill install affaan-m/ECC 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/affaan-m/ECC.git skills-src && mkdir -p .claude/skills && cp -r skills-src/docs/ja-JP/skills/github-ops .claude/skills/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
github-ops
GitHub stars
274k
Token cost
~1.1k tokens
SKILL.md length
428 words
Files
1
Skills in repo
657
Repo updated
First seen
Licence
MIT

At a glance

GitHub操作、自動化、APIインテグレーション、およびCI/CDワークフロー. An agent skill from affaan-m/ECC.

  • Works in 7 steps: Read the issue title, body, and comments → Check if it duplicates an existing issue… → Apply appropriate labels via gh issue… → …
  • Tasks that involve CI/CD
  • SKILL.md covers When to Activate, Tool Requirements, Issue Triage and PR Management, plus 4 more sections
  • Calls gh

What it does

GitHub Ops is an agent skill from affaan-m/ECC. GitHub操作、自動化、APIインテグレーション、およびCI/CDワークフロー。

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering CI/CD. It works with GitHub. The repository describes itself as: The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond. The licence is MIT.

When your agent uses it

  • Tasks that involve CI/CD

Example prompts

  • “/github-ops”

Workflow steps

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

  1. Read the issue title, body, and comments
  2. Check if it duplicates an existing issue (search by keywords)
  3. Apply appropriate labels via gh issue edit --add-label
  4. For questions: draft and post a helpful response
  5. For bugs needing more info: ask for reproduction steps
  6. For good first issues: add good-first-issue label
  7. For duplicates: comment with link to original, add duplicate label

What it can do on your machine

Read from SKILL.md and the folder at commit ef648e0. 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:

    • gh

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

  • Network

    No URLs in SKILL.md. Its commands use 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

GitHub Ops loads about 1.1k tokens when it runs. Until then it costs about 13 tokens; SKILL.md has 428 words of instructions outside code blocks.

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

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 affaan-m/ECC at commit ef648e0, republished under its MIT licence (© affaan-m). 428 words, ~1,107 tokens.

Download SKILL.mdSave it as .claude/skills/github-ops/SKILL.md (or your agent's skills folder).
name
github-ops
description
GitHub操作、自動化、APIインテグレーション、およびCI/CDワークフロー。
origin
ECC

GitHub Operations

Manage GitHub repositories with a focus on community health, CI reliability, and contributor experience.

When to Activate

  • Triaging issues (classifying, labeling, responding, deduplicating)
  • Managing PRs (review status, CI checks, stale PRs, merge readiness)
  • Debugging CI/CD failures
  • Preparing releases and changelogs
  • Monitoring Dependabot and security alerts
  • Managing contributor experience on open-source projects
  • User says "check GitHub", "triage issues", "review PRs", "merge", "release", "CI is broken"

Tool Requirements

  • gh CLI for all GitHub API operations
  • Repository access configured via gh auth login

Issue Triage

Classify each issue by type and priority:

Types: bug, feature-request, question, documentation, enhancement, duplicate, invalid, good-first-issue

Priority: critical (breaking/security), high (significant impact), medium (nice to have), low (cosmetic)

Triage Workflow
  1. Read the issue title, body, and comments
  2. Check if it duplicates an existing issue (search by keywords)
  3. Apply appropriate labels via gh issue edit --add-label
  4. For questions: draft and post a helpful response
  5. For bugs needing more info: ask for reproduction steps
  6. For good first issues: add good-first-issue label
  7. For duplicates: comment with link to original, add duplicate label
bash
# Search for potential duplicates
gh issue list --search "keyword" --state all --limit 20

# Add labels
gh issue edit <number> --add-label "bug,high-priority"

# Comment on issue
gh issue comment <number> --body "Thanks for reporting. Could you share reproduction steps?"

PR Management

Review Checklist
  1. Check CI status: gh pr checks <number>
  2. Check if mergeable: gh pr view <number> --json mergeable
  3. Check age and last activity
  4. Flag PRs >5 days with no review
  5. For community PRs: ensure they have tests and follow conventions
Stale Policy
  • Issues with no activity in 14+ days: add stale label, comment asking for update
  • PRs with no activity in 7+ days: comment asking if still active
  • Auto-close stale issues after 30 days with no response (add closed-stale label)
bash
# Find stale issues (no activity in 14+ days)
gh issue list --label "stale" --state open

# Find PRs with no recent activity
gh pr list --json number,title,updatedAt --jq '.[] | select(.updatedAt < "2026-03-01")'
Show full SKILL.md (161 more words)Show less

CI/CD Operations

When CI fails:

  1. Check the workflow run: gh run view <run-id> --log-failed
  2. Identify the failing step
  3. Check if it is a flaky test vs real failure
  4. For real failures: identify the root cause and suggest a fix
  5. For flaky tests: note the pattern for future investigation
bash
# List recent failed runs
gh run list --status failure --limit 10

# View failed run logs
gh run view <run-id> --log-failed

# Re-run a failed workflow
gh run rerun <run-id> --failed

Release Management

When preparing a release:

  1. Check all CI is green on main
  2. Review unreleased changes: gh pr list --state merged --base main
  3. Generate changelog from PR titles
  4. Create release: gh release create
bash
# List merged PRs since last release
gh pr list --state merged --base main --search "merged:>2026-03-01"

# Create a release
gh release create v1.2.0 --title "v1.2.0" --generate-notes

# Create a pre-release
gh release create v1.3.0-rc1 --prerelease --title "v1.3.0 Release Candidate 1"

Security Monitoring

bash
# Check Dependabot alerts
gh api repos/{owner}/{repo}/dependabot/alerts --jq '.[].security_advisory.summary'

# Check secret scanning alerts
gh api repos/{owner}/{repo}/secret-scanning/alerts --jq '.[].state'

# Review dependency bumps — merging is a user-authorized action (propose, never auto-merge)
gh pr list --label "dependencies" --json number,title
  • Review safe dependency bumps and propose merges for user approval — never auto-merge
  • Flag any critical/high severity alerts immediately
  • Check for new Dependabot alerts weekly at minimum

Quality Gate

Before completing any GitHub operations task:

  • all issues triaged have appropriate labels
  • no PRs older than 7 days without a review or comment
  • CI failures have been investigated (not just re-run)
  • releases include accurate changelogs
  • security alerts are acknowledged and tracked

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

Files

Just SKILL.md in docs/ja-JP/skills/github-ops of affaan-m/ECC.

Open the folder on GitHubat commit ef648e0

Compare with similar skills

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.

GitHub Ops compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
GitHub Ops this skillaffaan-m/ECC274k—~1.1kAutomated safety check: PassMIT
Azure Pipelines Log Downloaderansible/ansible71k—~825Automated safety check: PassGPL-3.0
CI Watchdoglatitude-dev/latitude-llm4.7k—~1.6kAutomated safety check: PassMIT
Released-kimuson/claude-code-viewer1.3k—~1.2kAutomated safety check: PassMIT
Megatron-LM CI Failure TriageNVIDIA/Megatron-LM18k—~1.6kAutomated safety check: PassApache-2.0
npm Release Via GitHub Actionsjmfederico/pi-web861—~2.9kAutomated safety check: PassMIT

Similar skills

  • Downloads Azure Pipelines CI logs for an Ansible pull request or build so the agent can analyze test failures, after asking you first.

    71k GitHub stars~825 tokensUpdated today
    DevOps & CloudAuto-check passed
  • CI Watchdog

    latitude-dev/latitude-llm

    Continuously monitor GitHub PR CI checks and automatically fix failures until all checks pass.

    4.7k GitHub stars~1.6k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Release

    d-kimuson/claude-code-viewer

    Run the claude-code-viewer release flow end-to-end. An agent skill from d-kimuson/claude-code-viewer.

    1.3k GitHub stars~1.2k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed
  • Official

    Investigates a failing GitHub Actions run or job for Megatron-LM, finds the root cause plus the PR and test author involved, and files a structured bug issue.

    18k GitHub stars~1.6k tokensUpdated today
    DevOps & CloudAuto-check passed
  • A skill your agent uses whenever the user asks for a new npm version, npm release, package release, new release, version bump, publishing to npm, cutting a GitHub release, tagging a release, or…

    861 GitHub stars~2.9k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Diagnoses and fixes failing GitHub Actions runs by identifying the failure, fetching only the relevant logs, finding the root cause and reproducing it locally.

    1.8k GitHub stars~1.9k tokensUpdated 5 days ago
    DevOps & CloudAuto-check passed

More from affaan-m/ECC

All 657 skills in this repo
  • Skill Stocktake

    affaan-m/ECC

    Audits your installed Claude skills and commands for quality, with a quick mode for recently changed skills and a full mode that evaluates all of them through subagents.

    274k GitHub starsUsed in 5 repos~1.9k tokens
    Auto-check passed
  • Videodb

    affaan-m/ECC

    Ingest, index, search, edit, and monitor video and audio with the VideoDB Python SDK — upload from files, URLs, or RTSP feeds, build spoken and scene indexes with timestamped search and playable…

    274k GitHub starsUsed in 3 repos~3.5k tokens
    Auto-check: notes
  • Rules Distillation

    affaan-m/ECC

    Scans installed skills for principles that recur across them and proposes rule-file changes: append, revise, add a section, create a file or leave as covered.

    274k GitHub starsUsed in 2 repos~2.3k tokens
    Auto-check passed
  • Builds DRAFT counterparty agreements from one markdown template and a small JSON spec per party, with clauses picked by the party's role.

    274k GitHub stars~2.9k tokensUpdated 2 days ago
    Auto-check passed
  • Measures whether agents actually follow a skill, rule or agent definition by generating scenarios at three strictness levels and scoring tool-call traces.

    274k GitHub starsUsed in 1 repo~623 tokens
    Auto-check passed
  • Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents.

    274k GitHub stars~3.5k tokensUpdated 2 days ago
    Auto-check passed

Works with

Questions about GitHub Ops

What does GitHub Ops do?

GitHub操作、自動化、APIインテグレーション、およびCI/CDワークフロー. An agent skill from affaan-m/ECC. GitHub Ops is an agent skill from affaan-m/ECC.

When should I use GitHub Ops?

GitHub Ops fits situations like: tasks that involve CI/CD.

How do I install GitHub Ops in Claude Code?

Run `npx skills add affaan-m/ECC --skill github-ops -a claude-code`. Or copy the skill folder (docs/ja-JP/skills/github-ops in affaan-m/ECC) into .claude/skills/github-ops in your project. Claude Code loads it when a task matches its description.

How do I install GitHub Ops in Codex?

Run `npx skills add affaan-m/ECC --skill github-ops -a codex`. Or copy the skill folder (docs/ja-JP/skills/github-ops in affaan-m/ECC) into .agents/skills/github-ops in your project. Codex loads it when a task matches its description.

Can I use 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 affaan-m/ECC --skill 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/github-ops, .gemini/skills/github-ops, .github/skills/github-ops and .opencode/skills/github-ops in your project.

What does GitHub Ops need to run?

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

Does GitHub Ops access the network?

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

Is 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 GitHub Ops use?

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 GitHub Ops use?

About 1.1k tokens (SKILL.md is roughly 4.4k 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 GitHub Ops?

Skills that share tags, products or a category with GitHub Ops: Azure Pipelines Log Downloader (ansible/ansible, 71k stars), CI Watchdog (latitude-dev/latitude-llm, 4.7k stars), Release (d-kimuson/claude-code-viewer, 1.3k stars) and Megatron-LM CI Failure Triage (NVIDIA/Megatron-LM, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains GitHub Ops?

affaan-m (a GitHub user) maintains it in affaan-m/ECC, which has 274,360 GitHub stars. The repository holds 657 skills in this directory. The repository was last updated on October 5, 2026.

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