affaan-m/ECC

github-ops

GitHub 仓库操作、自动化与管理。使用 gh CLI 进行问题分类、PR 管理、CI/CD 操作、发布管理和安全监控。当用户想要管理 GitHub 问题、PR、CI 状态、发布、贡献者、过期项目或任何超出简单 git 命令的 GitHub 操作任务时使用。

76Collecting
See how to use itView GitHub source
npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/github-ops"
Automated source guide

Source checked Jul 28, 2026·Refresh due Oct 26, 2026

Reorganized from the pinned upstream SKILL.md

Turn github-ops's source instructions into a guide you can follow

According to the pinned SKILL.md from affaan-m/ECC: 管理 GitHub 仓库,重点关注社区健康、CI 可靠性和贡献者体验。

npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/github-ops"
Check the pinned source

Best fit

  • GitHub 仓库操作、自动化与管理。使用 gh CLI 进行问题分类、PR 管理、CI/CD 操作、发布管理和安全监控。当用户想要管理 GitHub 问题、PR、CI 状态、发布、贡献者、过期项目或任何超出简单 git 命令的 GitHub 操作任务时使用。

Bring this context

  • A concrete task that matches the documented purpose of github-ops.
  • The files, examples, or context the task depends on.
  • Your constraints, target environment, and definition of done.

Expected outputs

  • A result that follows the pinned github-ops instructions.
  • A concise record of assumptions, inputs used, and unresolved questions.
  • A final check against the source workflow and relevant permission signals.

Key source sections

Read github-ops through these 5 source sections

Sections are extracted automatically from the pinned SKILL.md and link back to the source.

02

Review and auto-merge safe dependency bumps

gh pr list --label "dependencies" --json number,title

SKILL.md · Review and auto-merge safe dependency bumps
审查并自动合并安全的依赖项更新立即标记任何严重/高严重性告警至少每周检查一次新的 Dependabot 告警
03

何时激活

对议题进行分类(分类、打标签、回复、去重) 管理 PR(审查状态、CI 检查、过期 PR、合并就绪状态) 调试 CI/CD 失败 准备发布和变更日志 监控 Dependabot 和安全告警 管理开源项目的贡献者体验 用户说“检查 GitHub”、“分类议题”、“审查 PR”、“合并”、“发布”、“CI 坏了”

SKILL.md · 何时激活
对议题进行分类(分类、打标签、回复、去重)管理 PR(审查状态、CI 检查、过期 PR、合并就绪状态)调试 CI/CD 失败
04

工具要求

所有 GitHub API 操作均使用 gh CLI 通过 gh auth login 配置仓库访问权限

SKILL.md · 工具要求
所有 GitHub API 操作均使用 gh CLI通过 gh auth login 配置仓库访问权限所有 GitHub API 操作均使用 gh CLI 通过 gh auth login 配置仓库访问权限
05

议题分类

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

SKILL.md · 议题分类
阅读议题标题、正文和评论检查是否与现有议题重复(通过关键词搜索)通过 gh issue edit --add-label 应用适当的标签

SkillSignal prompt templates

Provide the task, context, and acceptance criteria

These prompts were written by SkillSignal from the source structure; they are not upstream text.

Task-start prompt

Confirm source fit, inputs, and outputs before acting.

Use github-ops to help me with: [specific task]. Context: [files, data, or background]. Constraints: [environment, scope, and prohibited actions]. Before acting, check the pinned SKILL.md and explain which sections apply, what inputs are still missing, and what you will deliver.

Source-guided execution

Make the Agent explicitly follow the key extracted sections.

Apply the pinned github-ops source to [task]. Pay particular attention to these source sections: “Re-run a failed workflow”, “Review and auto-merge safe dependency bumps”, “何时激活”, “工具要求”, “议题分类”. Preserve the important decision at each step. Mark facts not covered by the source as “needs confirmation” instead of inventing them. Then verify the result against my acceptance criteria: [criteria].

Result-review prompt

Check omissions, permissions, and source drift before delivery.

Review the current github-ops result: (1) does it satisfy the original task; (2) were any applicable steps or limits in the pinned SKILL.md missed; (3) did it perform any unauthorized file, command, network, or data action; and (4) which conclusions remain unverified? List issues first, then fix only what the source or user authorization supports.

Output checklist

Verify each item before delivery

The task matches the purpose documented in the SKILL.md.

The source section “Re-run a failed workflow” has been checked.

The source section “Review and auto-merge safe dependency bumps” has been checked.

The source section “何时激活” has been checked.

The source section “工具要求” has been checked.

Inputs, constraints, and acceptance criteria are explicit.

Unverified facts, compatibility, and outcome claims are clearly marked.

Any file, command, network, or data action has been reviewed.

Choose a different workflow

When another Skill is the better fit

FAQ

What does github-ops do?

管理 GitHub 仓库,重点关注社区健康、CI 可靠性和贡献者体验。

How do I start using github-ops?

The catalog detected this source-specific install command: npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/github-ops". Inspect the command and pinned source before running it.

Which Agent platforms does it declare?

No dedicated Agent platform is declared in the pinned source record.

Repository stars
234,327
Repository forks
35,711
Quality
76/100
Source repository last pushed

Quality breakdown

Based on traceable docs and repository signals; stars are not treated as quality.

76/100
Documentation25/30
Specificity14/25
Maintenance20/20
Trust signals17/25

Compare before choosing

Related Agent Skills and source variants

These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.

github-ops by affaan-m

GitHub repository operations, automation, and management. Issue triage, PR management, CI/CD operations, release management, and security monitoring using the gh CLI. Use when the user wants to manage GitHub issues, PRs, CI status, releases, contributors, stale items, or any GitHub operational task beyond simple git commands.

geofeed-tuner by github

Use this skill whenever the user mentions IP geolocation feeds, RFC 8805, geofeeds, or wants help creating, tuning, validating, or publishing a self-published IP geolocation feed in CSV format. Intended user audience is a network operator, ISP, mobile carrier, cloud provider, hosting company, IXP, or satellite provider asking about IP geolocation accuracy, or geofeed authoring best practices. Helps create, refine, and improve CSV-format IP geolocation feeds with opinionated recommendations beyon

laravel-horizon by event4u-app

Use when working with Laravel queues in production — Horizon dashboard, worker supervision, job metrics, balancing strategies — even when the user just says 'my jobs are piling up'.

mle-workflow by affaan-m

Production machine-learning engineering workflow for data contracts, reproducible training, model evaluation, deployment, monitoring, and rollback. Use when building, reviewing, or hardening ML systems beyond one-off notebooks.

simpy by k-dense-ai

Build, inspect, test, and analyze bounded process-based discrete-event simulations with SimPy, including events, resources, interrupts, monitoring, replications, warm-up, and reproducible output analysis.

View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 1 min

GitHub 操作

管理 GitHub 仓库,重点关注社区健康、CI 可靠性和贡献者体验。

何时激活

  • 对议题进行分类(分类、打标签、回复、去重)
  • 管理 PR(审查状态、CI 检查、过期 PR、合并就绪状态)
  • 调试 CI/CD 失败
  • 准备发布和变更日志
  • 监控 Dependabot 和安全告警
  • 管理开源项目的贡献者体验
  • 用户说“检查 GitHub”、“分类议题”、“审查 PR”、“合并”、“发布”、“CI 坏了”

工具要求

  • 所有 GitHub API 操作均使用 gh CLI
  • 通过 gh auth login 配置仓库访问权限

议题分类

按类型和优先级对每个议题进行分类:

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

优先级: critical(破坏性/安全相关), high(重大影响), medium(锦上添花), low(外观/体验优化)

分类工作流程

  1. 阅读议题标题、正文和评论
  2. 检查是否与现有议题重复(通过关键词搜索)
  3. 通过 gh issue edit --add-label 应用适当的标签
  4. 对于问题:起草并发布有帮助的回复
  5. 对于需要更多信息的 Bug:要求提供复现步骤
  6. 对于适合新手的议题:添加 good-first-issue 标签
  7. 对于重复议题:评论并附上原始议题链接,添加 duplicate 标签
# 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 管理

审查清单

  1. 检查 CI 状态:gh pr checks <number>
  2. 检查是否可合并:gh pr view <number> --json mergeable
  3. 检查 PR 的创建时间和最后活动时间
  4. 标记超过 5 天未审查的 PR
  5. 对于社区 PR:确保包含测试并遵循项目规范

过期策略

  • 超过 14 天无活动的议题:添加 stale 标签,评论要求更新
  • 超过 7 天无活动的 PR:评论询问是否仍在进行
  • 30 天内无回复的过期议题自动关闭(添加 closed-stale 标签)
# 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")'

CI/CD 操作

当 CI 失败时:

  1. 检查工作流运行:gh run view <run-id> --log-failed
  2. 识别失败的步骤
  3. 判断是不稳定测试还是真正的失败
  4. 对于真正的失败:确定根本原因并提出修复建议
  5. 对于不稳定测试:记录模式以便未来调查
# 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

发布管理

准备发布时:

  1. 确保主分支上的所有 CI 检查通过
  2. 审查未发布的更改:gh pr list --state merged --base main
  3. 根据 PR 标题生成变更日志
  4. 创建发布:gh release create
# 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"

安全监控

# 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 and auto-merge safe dependency bumps
gh pr list --label "dependencies" --json number,title
  • 审查并自动合并安全的依赖项更新
  • 立即标记任何严重/高严重性告警
  • 至少每周检查一次新的 Dependabot 告警

质量门禁

在完成任何 GitHub 操作任务之前:

  • 所有已分类的议题都带有适当的标签
  • 没有超过 7 天未收到审查或评论的 PR
  • CI 失败已被调查(不仅仅是重新运行)
  • 发布包含准确的变更日志
  • 安全告警已被确认并跟踪
Source repo
affaan-m/ECC
Skill path
docs/zh-CN/skills/github-ops/SKILL.md
Commit SHA
4e973d3eaf92
Repository license
MIT
Data collected