github-ops skill
scripts리포지토리 생성, 릴리스 관리, Issue/PR 처리 및 README 작성을 포함한 GitHub 원격 작업을 관리합니다.
- GitHub 스타
- 81
- 파일
- 18
- 마지막 커밋
- 2026년 11월 7일
- 라이선스
- MIT
- 허용된 도구
- 6
github-ops skill은 무엇을 하나요?
리포지토리 생성, 릴리스 관리, Issue/PR 처리 및 README 작성을 포함한 GitHub 원격 작업을 관리합니다.
skill의 SKILL.md에서 생성된 요약입니다.
github-ops skill 정보
원격 리포지토리를 관리하는 개발자는 이 SKILL을 사용하여 GitHub 작업을 자동화하고 고품질의 문서를 유지할 수 있습니다. 특정 공개 설정이 적용된 초기 리포지토리 생성부터 복잡한 릴리스 워크플로우 관리까지 프로젝트의 전체 라이프사이클을 처리합니다. 이 SKILL은 GitHub CLI를 사용하여 리포지토리 생성, Issue 및 Pull Request 관리, 변경 로그에서 추출한 자동화된 노트를 포함한 릴리스 게시 등의 작업을 수행합니다.
단순한 명령 실행을 넘어, 프로젝트가 전문적으로 보일 수 있도록 README 작성에 특화되어 있습니다. 소개글 초안 작성, 쇼케이스 또는 레퍼런스 스타일의 랜딩 페이지 레이아웃 구축, 그리고 매 릴리스마다 최신 상태를 유지하는 Recent Updates 섹션 관리가 가능합니다. 보안과 품질을 위해 메타데이터 완성도와 문서 표준을 기준으로 리포지토리를 점수화하는 읽기 전용 감사 모드도 포함되어 있습니다. 모든 원격 작업이 필요한 로컬 체크와 적절한 버전 관리 로직을 거치도록 git-ops 및 push-preflight 도구와 함께 작동하도록 설계되었습니다.
agent가 수행할 수 있는 작업
- 1새 리포지토리 게시전문적인 README, 적절한 토픽 및 초기 릴리스가 포함된 새로운 GitHub 리포지토리를 생성합니다.
- 2소프트웨어 릴리스 자동화커밋 히스토리를 기반으로 버전 업데이트, 변경 로그 업데이트 및 GitHub 릴리스를 생성합니다.
- 3리포지토리 상태 감사읽기 전용 스코어카드를 실행하여 리포지토리가 문서화 및 메타데이터 표준을 준수하는지 확인합니다.
- 4README 문서 유지 관리새 버전이 출시될 때마다 README의 Recent Updates 섹션을 자동으로 업데이트합니다.
skill의 SKILL.md를 기반으로 작성되었습니다. 모든 사용 사례는 해당 문서의 인용구와 대조 확인되었습니다.
github-ops skill 설치 방법
각 명령은 skill 폴더를 클라이언트의 skills 디렉터리에 복사합니다. 클라이언트를 재시작하거나 새 세션을 시작하여 로드하세요.플러그인에 github-ops skill 설치
/plugin marketplace add 0xDarkMatter/claude-mods /plugin install claude-mods@claude-mods
Claude Code에 github-ops skill 설치
~/.claude/skills/github-ops/SKILL.md
$ npx degit 0xDarkMatter/claude-mods/skills/github-ops ~/.claude/skills/github-opsClaude Code (project)에 github-ops skill 설치
.claude/skills/github-ops/SKILL.md
$ npx degit 0xDarkMatter/claude-mods/skills/github-ops .claude/skills/github-opsCodex에 github-ops skill 설치
~/.agents/skills/github-ops/SKILL.md
$ npx degit 0xDarkMatter/claude-mods/skills/github-ops ~/.agents/skills/github-opsGemini CLI에 github-ops skill 설치
~/.gemini/skills/github-ops/SKILL.md
$ npx degit 0xDarkMatter/claude-mods/skills/github-ops ~/.gemini/skills/github-opsClaude.ai에 github-ops skill 설치
npx degit 0xDarkMatter/claude-mods/skills/github-ops github-ops && zip -r github-ops.zip github-ops # claude.ai → Customize → Skills → + → Create skill → Upload a skill → github-ops.zip
자동 검사
2026년 11월 15일에 실행됨전체 보고서 →아직 검증되지 않았습니다. 스킬은 점수 80, 심각한 발견 없음, 검사에 충분한 데이터가 필요합니다. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능0xdarkmatter/claude-mods/skills/github-ops is public and reachablegithub.com/0xdarkmatter/claude-mods/tree/HEAD/skills/github- ↗통과
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit 2026-11-07github.com/0xdarkmatter/claude-mods/commits ↗통과
- 스크립트에 다운로드 후 실행이나 자격 증명 탈취가 없음3 scripts read; no download-and-run, remote eval, base64 execution or credential upload통과
- SKILL.md에 숨겨진 지침 없음No override phrases, safeguard switches, credential requests or hidden charactersgithub.com/0xdarkmatter/claude-mods/blob/HEAD/skills/github- ↗통과
- 사전 허용 도구가 제한됨Bash lets the agent run any shell command without askinggithub.com/0xdarkmatter/claude-mods/blob/HEAD/skills/github- ↗결함 발견
- SKILL.md가 Agent Skills 형식을 따름Valid name and description; says when to use it; 264 linesgithub.com/0xdarkmatter/claude-mods/blob/HEAD/skills/github- ↗통과
SKILL.md
GitHub에서 보기GitHub Ops
GitHub-side operations skill. Owns everything that talks to api.github.com via gh CLI: repo creation, metadata configuration, releases, and the conventions that govern how 0xDarkMatter repos present on GitHub.
Sits alongside two related skills:
LOCAL BRIDGE REMOTE (GitHub)
───── ────── ───────────────
git-ops push-preflight github-ops (this skill)
Ownership by concern, row by row: references/delegation-and-authorship.md.
Hard rules
- Visibility defaults to private. Pass
--privatetogh repo createunless the user has explicitly said "public" / "make it public" for this specific repo. Seereferences/repo-visibility.md. - Major version bumps require explicit approval. Default to minor; patch for fix-only ranges. Never auto-suggest a 1.0.0 from
BREAKING CHANGE:markers — surface and ask. Seereferences/release-strategy.md. - Always run
push-preflightbefore any push to a remote. No exceptions. If push-preflight refuses, do not proceed — fix the cause and re-run. - Delegate local git operations to
git-ops. Don't reimplement commit/tag/push logic. github-ops orchestrates the GitHub-side calls (gh) and the README/CHANGELOG edits; git-ops handles git itself. - README "Recent Updates" updates on every release. This is the one README touch that always happens, regardless of how minor the release. See
references/readme-recent-updates.mdfor the canonical claude-mods style. - Never push without confirming visibility decision. When creating a new repo, surface visibility as a flippable line in the plan ("creating as private — say 'public' to flip"), not buried in flag soup.
- No local-machine paths in committed content. Never bake
C:\Users\<name>\…,/home/<name>/…,/Users/<name>/…,/tmp/<one-off-test-dir>, or any other machine-specific path into README entries, Recent Updates bullets, CHANGELOG entries, release notes, tag annotations, or commit messages. Public release artefacts have to read the same on someone else's machine. Use generic placeholders (~/Temp/,<temp-dir>, "a temp directory") or describe the file's purpose abstractly instead. If a path genuinely is part of the project's public API (install location, config path), state it canonically ($HOME/.claude/skills/...), not as a literal absolute that includes a user name. - Preview every public post before sending. Anything with author voice that lands on a third-party surface —
gh issue create/comment/edit --body,gh pr create/comment/review/edit --body,gh release create --notes, merge commit--subject/--body— must be quoted verbatim in chat with the exact send command named, then await explicit approval before invoking. Mechanical actions with no body (label, assign, milestone, mark-ready, close-without-message) skip preview. See~/.claude/rules/public-posts.mdfor the full rule.
Three modes
Mode new — first publish of a repo
Triggered by: "publish to github", "create repo on github", "push to github" (when no origin remote exists), "ship this repo".
1. Audit (run mode `audit` checklist; abort on critical fail)
- LICENSE present?
- README has tagline + install + quickstart?
- pyproject.toml / package.json has description, keywords, license, repository URL?
- At least one tag exists (typically v0.1.0)?
- CHANGELOG.md has an entry for the latest tag?
2. Draft / refine README intro (2–3 paragraphs) — see references/readme-description.md
- Tagline only or under 80 words: draft 2–3 paragraphs (what / why / for whom) from
metadata, CHANGELOG and the entry point, never fabricated; get approval first.
Detail: references/readme-steps.md
- Commit via git-ops with: docs: Expand README intro
2b. Build the landing-page layer — see references/readme-landing-page.md
The intro answers "what is this"; this step answers the other three questions a
cold visitor asks in their first ten seconds (is it alive / what do I get /
what does it look like). Benefits before mechanics.
FIRST pick the register, and surface it as a flippable line like visibility:
"Laying the README out as **Reference** — say 'showcase' to flip"
- Showcase — reader is deciding WHETHER to adopt. Apps, dashboards, TUIs,
generators, anything with visible output. Visual high, Features above Install,
airier prose.
- Reference — reader has already decided and needs to USE it. Libraries, SDKs,
plain-output CLIs, internal tooling. Install + a real usage example in the
first screenful; Features denser and lower.
Tie-breakers: output is visible → Showcase. It's a dependency of other code →
Reference. Register controls emphasis and density, NEVER honesty — Showcase is
not permission for marketing verbs; the readme-description.md anti-patterns
apply identically to both. Never mix the two.
Then, in either register: badge row, Features above Install written as benefits,
and a screenshot only if there is a visual surface. Rules: references/readme-steps.md
- Surface the layout to the user with the intro draft; commit together.
3. Add "Recent Updates" section to README if missing
- Use claude-mods style by default (see references/readme-recent-updates.md)
- Place after Quickstart, before deep "why this exists" sections — i.e. below the
Features + visual added in step 2b (see references/readme-landing-page.md for the
full section order and why liveness sits there, not above Features)
- For first release, single bullet block describing the initial extraction
- Commit via git-ops with: docs: Add Recent Updates section
4. Surface the publish plan to user, with visibility as a flippable line:
"Creating as **private** at github.com/<org>/<repo> — say 'public' to flip"
Wait for explicit confirmation.
5. Create the repo:
gh repo create <org>/<repo> --private --source=. --remote=origin \
--description "<one-line — distilled from the README intro draft in step 2, ≤ 350 chars>" \
--homepage "<homepage URL or omit>"
(NEVER pass --push; we want push-preflight to run between)
Note: the GitHub `--description` is a single line and distinct from the README intro.
Derive it FROM the intro you just wrote, not from package metadata blindly.
6. Run push-preflight:
bash $HOME/.claude/skills/push-preflight/scripts/preflight.sh --cwd <repo> origin main
On any non-zero exit: stop, report, do not push.
7. Push main + tags:
git -C <repo> push -u origin main
git -C <repo> push origin --tags
8. Set topics (derived from package keywords + language + frameworks):
gh repo edit <org>/<repo> --add-topic <t1> --add-topic <t2> ...
Aim for 6–12 topics. See references/metadata-checklist.md for derivation.
9. Create the release for the latest tag:
gh release create <tag> --title "<tag> — <one-line headline>" \
--notes "$(extract from CHANGELOG.md)"
10. Verify:
gh repo view <org>/<repo>
gh release view <tag>
Report URL to user.
Mode update — subsequent release
Triggered by: "ship a release", "cut a release", "release v0.X.Y", "publish update".
1. Audit current state vs last release:
git -C <repo> log $(git describe --tags --abbrev=0)..HEAD --oneline
Categorise commits by Conventional Commits prefix.
2. Determine version bump (see references/release-strategy.md):
- Any feat: → minor (default)
- Only fix:/chore:/docs:/perf:/style:/test: → patch
- Any BREAKING CHANGE: or !: → STOP, ask user, never auto-major
3. Update CHANGELOG.md:
New section for the new version with categorised changes (Added/Changed/Fixed/Removed).
Delegate the file edit + commit to git-ops with: docs: CHANGELOG for v<N>
4. Update README "Recent Updates":
Prepend a new version block (claude-mods style) at the top of the section.
Trim oldest if section exceeds 7 versions.
Bullets per change, emoji + bold tagline + 1-3 sentence prose.
See references/readme-recent-updates.md for the emoji vocabulary.
Minor: Recent Updates, plus body sections only for new commands/config/install.
Patch: Recent Updates only. Thin or stale intro: propose an expansion. Detail:
references/readme-steps.md
Landing-page touch-ups (see references/readme-landing-page.md) — act only on a
real trigger, never as routine churn. Keep the README's EXISTING register
(Showcase vs Reference); never switch it silently. A genuine audience change
(internal tool going public) is worth proposing a switch — done all at once,
with approval — not drifting into one bullet at a time:
- Triggers: a new capability, a red or stale badge, a screenshot a UI change made
wrong, a visual surface with no visual. Detail: references/readme-steps.md
5. Commit README + CHANGELOG via git-ops:
docs: Recent Updates + CHANGELOG for v<N>
6. Create local tag via git-ops:
git tag -a v<N> -m "v<N>"
7. Run push-preflight:
bash $HOME/.claude/skills/push-preflight/scripts/preflight.sh --cwd <repo> origin <branch>
On any non-zero exit: stop, report, do not push.
8. Push commits + tag:
git push origin <branch>
git push origin v<N>
9. Create GitHub release:
gh release create v<N> --title "v<N> — <headline>" \
--notes "$(extract CHANGELOG section for v<N>)"
10. Verify:
gh release view v<N>
Report URL to user.
Mode audit — read-only checklist
Triggered by: "audit github repo", "is this repo ready to publish", "check repo metadata", "score this repo", "how healthy is this repo", "score the fleet".
Start with bash scripts/repo-scorecard.sh --repo <o>/<r> (--org <org> for a fleet, --min-score N as a CI gate): a strictly read-only 0–100 score and grade per repo with its top 3 fixes. The checklist below is what it rolls up. Rubric and exit codes: references/auditor-scripts.md.
Below is the underlying checklist the scorecard's dimensions roll up (and what mode new/update act on). See references/metadata-checklist.md for the complete version; the SKILL enforces these:
LOCAL FILE CHECKS
[ ] LICENSE file present + matches metadata
[ ] README has: tagline, install, quickstart, license link
[ ] README intro is ≥ 80 words (2–3 paragraphs orienting a cold reader)
[ ] README has "Recent Updates" section near top
LANDING-PAGE CHECKS — all WARN-level, never a hard fail (references/readme-landing-page.md)
[~] Infer the README's REGISTER first (Showcase = pitch-forward, visual high, Features
above Install; Reference = install + usage in the first screenful, denser Features)
and judge every row below against THAT register. A Reference README is not missing
a hero — it declined one. WARN if the register is visibly mixed (a Showcase hero
bolted onto a Reference body, or vice versa): it serves neither reader.
[~] README has a badge row under the title (≤ 5 badges; license + at least one
liveness signal — CI or version). WARN if absent; WARN if > 7 badges (badge wall)
or if a CI badge points at a workflow with no runs / a red default branch.
[~] README has a "## Features" (or equivalent) section ABOVE Install, with bullets
that lead with what the reader GETS, not what the software contains. WARN if the
section is missing, or if it is a component inventory / a flag-by-flag table.
[~] README has a screenshot or demo — CONDITIONAL. Only warn when the project has a
visual surface (TUI, GUI, dashboard, web UI, rendered/generated output, or
colourised CLI output). A plain-text CLI, a library, an SDK, or a config/skill
bundle legitimately has none: report nothing, do not nag. Where images exist,
WARN on missing alt text or a light-only capture with no <picture> dark variant.
[ ] CHANGELOG.md present and has entry for latest tag
[ ] pyproject.toml / package.json: description, keywords, license, repository URL, homepage
[ ] Latest tag matches version in package metadata
GITHUB STATE + SECURITY POSTURE CHECKS: description, homepage, topics, main branch,
releases; security via scripts/check-security-posture.sh. Rows:
references/auditor-scripts.md; complete list: references/metadata-checklist.md
Output: per-row pass/fail/warn, then a summary score and list of fixes. Fixes are suggested but not applied — the user decides whether to run mode new or mode update to act on them. For the security-posture rows, run scripts/check-security-posture.sh --repo <o>/<r> and fold its checklist in; the enable commands it emits are surfaced for the user to approve, never auto-run.
Operations
Atomic GH-side actions that don't fit the three multi-step modes. Each operation that writes author voice to a third-party surface (issue/PR body, comment, review body, release notes, merge commit subject/body) is governed by hard rule 8 and public-posts: quote the exact body in chat, name the send command, wait for explicit approval, then send. Mechanical actions (labels, assign, close-without-message, mark-ready) skip preview.
Issues
Reads need no preview. Author-voice writes (create, comment, edit title/body, a closing comment) are preview-gated; label, assign, milestone, close/reopen and transfer are mechanical. Table: references/operations-preview.md; playbooks: references/issue-ops.md.
Pull Requests
Reads need no preview. Create, comment, review and edit title/body are preview-gated; labels, reviewers and mark-ready are mechanical. Merge needs explicit user approval and the pre-merge gate below. Table: references/operations-preview.md.
PR creation lives here, not in git-ops. git-ops handles local commits/branches/push; the gh pr create call itself talks to api.github.com and belongs in this skill. (Existing git-ops T2 PR-create still works; new flows should route through github-ops.)
Pre-merge gate — never invoke gh pr merge without first confirming:
gh pr view <n> --json mergeable,mergeStateStatus→mergeable: MERGEABLE,mergeStateStatus: CLEANgh pr checks <n>→ every check passed (or explicitly ignored with user approval)gh pr diff <n>reviewed — confirm no surprise scope, no committed secrets/local paths, no stale PR-body claims- Merge strategy picked — default squash for fix/feature branches with multiple WIP commits;
--mergeonly when individual commits matter;--rebasefor linear-history repos. Ask if uncertain. - Branch deletion is a separate explicit step, not bundled. Default to keeping the branch; delete remote + local after merge only on explicit user OK (it's destructive enough to warrant its own confirmation, and a checked-out branch can't be deleted).
See references/pr-ops.md for full playbooks, review-flow templates, and the merge-strategy decision tree.
Conventions enforced (load reference files for detail)
Defaults: minor on feat:, patch on fix:-only, major only with approval; README intro of 2–3 concrete paragraphs; landing page register-first, never mixed; Recent Updates in per-version blocks; --private unless told public; preview-gated issue/PR bodies, squash by default, branch deletion a separate step. The reference behind each: references/files.md.
Authorship, delegation, expansion
For 0xDarkMatter repos set repo-local user.name / user.email before any commit; rewriting authorship is safe only before the first push. github-ops runs the gh calls and README/CHANGELOG edits, git-ops the commits, tags and pushes, push-preflight the preflight. Unbuilt expansions (Actions, secrets, branch-protection writes) follow the same boundary: api.github.com here, purely local to git-ops. Commands and diagram: references/delegation-and-authorship.md.
Files
| File | Role |
|---|---|
references/readme-landing-page.md |
The layer between intro and changelog — the Showcase/Reference register choice, section order for each, badge row (shields.io + labelColor), features-as-benefits with a before/after rewrite, screenshot/demo policy, landing-page anti-patterns |
| Every other reference, script and asset | The role of each: references/files.md |
Read-only auditors (the blind spots)
bash scripts/check-issues.sh --repo <o>/<r> surfaces external and stale open issues you would otherwise miss (push-preflight runs it advisory on every push). bash scripts/check-security-posture.sh --repo <o>/<r> (--org, --commands) audits Dependabot, secret and code scanning, private vulnerability reporting, SECURITY.md and branch protection. Neither applies a change: enable commands are text you review and run under hard rule 8. Exit 10 = something to look at. Detail: references/auditor-scripts.md.
이 스킬의 파일
18github-ops skill 질문
Claude Code에 github-ops skill을 어떻게 설치하나요?
npx degit 0xDarkMatter/claude-mods/skills/github-ops ~/.claude/skills/github-ops를 실행합니다. Claude Code는 ~/.claude/skills(모든 프로젝트) 또는 .claude/skills(한 프로젝트)에서 skills를 로드하며, 설명이 작업과 일치할 때 skill을 사용합니다.
github-ops skill을 사용할 수 있는 클라이언트는 무엇인가요?
Agent Skills 형식을 읽는 모든 클라이언트(Claude Code, Codex, Gemini CLI, claude.ai(ZIP으로 업로드))가 사용할 수 있습니다. skill 내 스크립트는 클라이언트가 코드 실행을 허용하는 경우에만 실행됩니다.
리포지토리 공개 범위는 어떻게 처리하나요?
사용자가 명시적으로 공개(public)를 요청하지 않는 한 리포지토리는 기본적으로 비공개(private)로 설정됩니다.
메이저 버전 업데이트 규칙은 무엇인가요?
메이저 버전 업데이트는 사용자의 명시적인 승인이 필요하며, 기본적으로는 마이너 또는 패치 버전으로 설정됩니다.
원격 저장소로 자동 푸시가 가능한가요?
아니요, 원격 저장소에 푸시하기 전에 반드시 push-preflight 체크를 실행해야 합니다.
공개 댓글이나 Issue는 어떻게 처리하나요?
제3자에게 노출되는 작성자 목소리가 포함된 모든 콘텐츠는 전송 전 채팅창에서 미리 보고 승인을 받아야 합니다.