#SkillRepo stars
- 433Cleanup Slopscomfuture/agent-skillsFind and simplify implicit state machines across a repository or a specified pull request without regressing behavior. Use for requests such as "find all of the implicit state machines in my app" or a cleanup pass that removes redundant state and consolidates scattered transitions for readability and maintenance.9
- 434Code Review Analyst1ikeadragon/awesome-offsec-claudePerform exploit-oriented code review by proving attacker-controlled paths from source to sink and validating impact.10
- 435Gh Autoreview Resolvecomfuture/agent-skillsRun a bounded GitHub automated-review and resolution loop for a specified pull request. Use when an agent must mark a PR ready for review, confirm the automated reviewer started through an eyes reaction, wait for a thumbs-up or concrete review response, validate and address review threads, request a narrowly focused `@codex review` follow-up when warranted, prevent review scope creep through PR comments or a gh-create-issue follow-up, and optionally merge with the user's preferred strategy.9
- 436Gh Create Issuecomfuture/agent-skillsCreate high-quality GitHub issues or issue drafts from repository evidence, user intent, and external documentation. Use when the user asks an agent to create, draft, file, open, or prepare an implementation issue, bug report, feature request, follow-up issue, or GitHub issue with researched facts, scope, non-goals, suggested direction, acceptance criteria, and validation notes.9
- 437Gh Implement Issuecomfuture/agent-skillsImplement GitHub issues through a complete branch-to-PR workflow. Use when the user asks an agent to implement, fix, or ship a specific GitHub issue, including reading issue comments, confirming the implementation contract, creating a branch, making atomic commits, validating, pushing, opening or updating a PR, and handling issue-linked review/CI follow-up. Use related skills or integrations when available; otherwise inspect the repository, issue, PR, CI, and review context directly with the available tools.9
- 438Solid Control Flow Renderinglvcoi/solidJSkillsSelect and enforce SolidJS control-flow and rendering primitives with explicit branch semantics. Use for conditional/list rendering, suspense boundaries, and dynamic rendering choices.9
- 439ShipreeltheBstar/shipreelTurn a pull request into a short narrated walkthrough video (about two and a half minutes) with animated diagrams, code panels, optional screen recordings of the real app, captions, crossfade cuts and an ambient music bed. Runs locally with no paid services by default. Use when asked for a PR video, PR walkthrough, demo video of a change, or "make a shipreel".3
- 440Git Lorekargnas/skillsCaptures, queries, and configures decision context in native Git trailers. Use for non-trivial commit messages, constraints, rejected alternatives, directives, test gaps, Lore history queries, or installing Lore rules in project or global agent instructions.9
- 441Oss Finderkargnas/skillsFinds battle-tested open-source repos, libraries, frameworks, CLI tools, or code on GitHub, ranked by README polish-days instead of stars. Also the shared GitHub code-search backend toolkit — rotating PAT pool, grep.app, Blackbird web index, BigQuery/GHArchive, and the code-search fallback chain. Use for 'find a library/framework/tool for X', 'battle-tested repo', GitHub-wide code search, or when `gh search code` rate-limits. Finding installable SKILL.md agent-skill packages goes to the skill-finder skill (it delegates its GitHub sweep here).9
- 442Conventional Commentsmilistu/agent-skillsFormat review comments following the Conventional Comments standard. Use when writing code review comments, PR feedback, RFC reviews, peer reviews, or when the user asks for help with review comments.9
- 443Conventional Commitsmilistu/agent-skillsGenerate commit messages following the Conventional Commits v1.0.0 specification with Angular convention types. Use when creating git commits, writing commit messages, or when the user asks for help with commit messages.9
- 444PR Messagemilistu/agent-skillsWrite a concise, high-signal GitHub pull request message that explains intent, impact, and risk9
- 445PR Reviewmilistu/agent-skillsAnalyze and explain a pull request to help review it effectively9
- 446Octo Ck Miromeshmakers/octo-claude-skillsVisualizes OctoMesh Construction Kits as UML class diagrams on a Miro board. Reads CK YAML definitions from a specified git branch in the local octo-construction-kit checkout (non-destructive via git show) and creates one detailed UML diagram per CK — types with attributes and datatypes, records, enums, inheritance arrows, associations with multiplicity, and cross-CK references. Lets the user pick a branch (default main) and choose between a new Miro board or adding to an existing board URL. Trigger on - visualize CK, visualize construction kit, CK diagram, CK to Miro, Miro board for CK, UML d10
- 447Octo Commitmeshmakers/octo-claude-skillsStructured workflow for committing finished work across OctoMesh repositories: scans repos for changes, resolves or creates the Azure DevOps work item, builds the AB# commit message and PR title (AB#<id> <Fix|New|Chore|Refactor|Test|Docs>: …), verifies the build/tests, and optionally opens a PR and hands it over for review: with octo-claude-pm installed its agent-operating-rules decide the CodeRabbit review rounds and the merge queue; the developer merges, never the agent. Enforces the review checkpoint — never pushes or opens a PR without explicit user approval in the current session. Trigger10
- 448Eveningthatmike1/claude-skillsEnd-of-day recap that proves what actually got done today — aggregates today's Claude Code sessions, git commits, and beads activity into an honest accomplishment log. The counter to the "I did nothing today" feeling. Use when user says evening, end of day, wrap up, recap today, "what did I actually do today", "did I do anything today", or feels like the day was a mess/wasted.10
- 449Readoutthatmike1/claude-skillsGenerate, update, and publish a "readout" — an MDX-authored, themed session document (walkthrough, plan, comparison, investigation, changelog) compiled to HTML and published to readout.ssscribe.app, where teammates leave anchored comments the agent reads back into the session. Successor to the artifact skill, built for sharing. Use when the user asks to "make/create/publish a readout", wants session output as a shareable link, asks to update an existing readout, or asks to read/check comments on a readout.10
- 450Sync to Githublingengyuan/my-skillsInspect, stage, commit, and push Git repository changes safely within authorized scope. Use when committing code, pushing to GitHub, inspecting staged diffs, creating commits, or drafting commit messages.9
- 451Wonder Pillthatmike1/claude-skillsTurns open-ended requests into things to think WITH instead of answers to accept. Audits the hidden assumptions inside a topic, inverts them into sharp "what if" provocations, branches each one outward, and delivers an interactive mind map (a standalone html file opened locally) plus the written wonderings. Use this whenever someone wants ideas, brainstorming, exploration, inspiration, or a direction to head in — "give me ideas for X", "help me brainstorm", "I'm stuck on what to do for my science fair / project / story / thesis", "what are some angles on X" — and especially when they seem to w10
- 452Git Guardrails Claude CodeGAGAA-HUE/ASHUO-claude-skillsSet up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.5
- 453Gitthechandanbhagat/claude-skillsGit operations, conflict resolution, history management, and Git workflows. Use for complex Git operations and version control tasks.9
- 454Code Review ZhRazorEdge-wyh/zh-skills审查代码时使用。按中文工程规范对代码做 review:命名、注释、可读性、错误处理、边界、安全、性能。特别关注中文项目里的拼音命名、翻译腔注释、神秘缩写。6
- 455Commit ZhRazorEdge-wyh/zh-skills写 git commit message 时使用。按 Conventional Commits 规范产出中文 commit message:类型 + 作用域 + 中文描述,动词开头,一行能看懂。特别适合中文团队统一提交风格。6
- 456Skill Auditortlzmw001/naiyue-skills审计第三方 skill 是否名副其实——给定 GitHub 链接或本地路径,抽取其宣称的功能为原子声称清单(claim list),在临时沙箱中通过多轮自迭代场景验证,逐条给出"证实/证伪/无法验证/受阻"结论,并结合设计解析做现象↔机制归因,最终产出证据可追溯的一致性审计报告。当用户想"测一下这个 skill"、"这个 skill 好不好用"、"验证某个 GitHub skill 是否靠谱"、"评估/审计一个 skill"、"帮我看看这个 skill 是不是虚标"时,务必使用本 skill,即使用户没有说出"审计"或"评估"字样。5
- 457Cmd Gh IssueOlshansk/agent-skillsCreate structured GitHub issues from conversation context using gh CLI9
- 458Cmd PR Build ContextOlshansk/agent-skillsBuild high-signal PR context for review with diff analysis, risk assessment, and discussion questions9
- 459Cmd PR Conflict ResolverOlshansk/agent-skillsResolve merge conflicts systematically with context-aware 3-tier classification and escalation protocol9
- 460Cmd PR DescriptionOlshansk/agent-skillsGenerate a PR title and description, then commit, create/update the PR on approval9
- 461Cmd PR EdgecaseOlshansk/agent-skillsReview branch changes for test gaps, logic edge cases, failure modes, and integration risks9
- 462Cmd PR Follow UpOlshansk/agent-skillsSelf-review after implementation — surface missed work, simplification opportunities, and idiomatic improvements9
- 463Cmd PR Gh CommentsOlshansk/agent-skillsHolistically triage and resolve GitHub PR review comments — gather comments with full line ranges, study surrounding code context (TODOs, docstrings, related logic), hunt for adjacent improvements via rg, execute an approval-gated plan, optionally refine AGENTS.md style rules, and propose cmd-olshanskify template updates when feedback comes from @olshansk9
- 464Cmd PR Review PrepareOlshansk/agent-skillsPrepare branch for code review by building context, identifying issues, and suggesting improvements9
- 465Cmd PR Scope SweepOlshansk/agent-skillsFinal pass to identify missed items, edge cases, and risks before considering a scope done9
- 466PR Reviewborkweb/skillsReview a GitHub PR and post its CRITICAL findings as line-anchored inline comments with suggestion blocks after you confirm; INFORMATIONAL findings stay in chat. Adds a second pass from the other harness when the diff needs one, reuses CI results, and reviews only new commits on a re-run. Invoke only when the user explicitly asks for /pr-review or for a PR review that posts comments, or when bork:do runs a review batch; never on your own. For a local diff or branch without posting, use review.9
- 467Reviewborkweb/skillsPre-landing review of a local diff, branch or PR for concrete defects, scope gaps and landing readiness, ending in SAFE TO LAND, LAND WITH CAUTION or DO NOT LAND. Use for 'review this', 'review my branch', 'is this safe to land' or 'check this diff'. To post comments on a GitHub PR use pr-review; for a security audit use review-security.9
- 468App Store Changeloghuytran1120/vietnam-agentic-skillsGenerate user-facing App Store release notes from git history since the last tag.9
- 469Dialog Treeikotelkin/claude-skillsMaintain a visual "dialog tree" — a data file plus a self-contained HTML viewer in the project repo that map the branches of a long conversation (user questions → the steps/variants of the answers) as an interactive tree with resolve/delete marks and a "built up to" marker for incremental updates. Use whenever the user asks to "create/set up a dialog tree", "update the tree", "add this to the tree", "show open branches", or mentions dialog-tree.html — and proactively offer it when a deep-dive discussion branches enough that the user risks losing track of unexplored side-threads.3
- 470Commit Flowyasunori0418/skills`git commit` / `git commit --amend` を実行する前、または「commit」「amend」「コミット」「コミットして」の一語・短文だけを渡された時点で必ず発火する git コミット実施ルール。理由や差分の説明が一切無くても、ファイル全文を読んでメッセージを組み立てる前に先に参照する。主目的は論理的に独立した修正を都度・適切な粒度でコミットすること。メッセージは Conventional Commits 形式、素材は同梱の決定論スクリプト commit-context.sh が出す staged diff のみ。「コミット分けて」と依頼される、独立した複数修正をまとめるか分けるか判断する、レビューコメント対応をコミットする、rebase / squash / cherry-pick 後のメッセージを整える、`gh pr create` の PR タイトルをコミット流儀へ揃える場面でも参照する。plan モードでのコミット計画の立案は commit-plan スキルの領分。9
- 471Commit Planyasunori0418/skills実装計画・リファクタリング計画・レビュー対応計画・並列作業のタスク分解など、計画を成果物として書き出すときに必ず参照するコミット計画ルール。plan モードでは ExitPlanMode で plan を提示する前に必須、計画ドキュメントや job-graph のタスク分解・エージェントへの指示文でも同様に適用する。計画成果物にコミット計画セクション(論理的に独立した修正単位での分割と Conventional Commits 形式のメッセージ)が無ければ実装に入らない。「実装計画を立てて」「planを立てて」「実行計画を作って」「リファクタリング計画を立てて」「コミット計画を立てて」「タスクを分解して」と依頼される、複数の独立した修正をまとめるか分けるか計画段階で判断する等の場面では、ユーザーが「コミット」に一切言及していなくても必ず発火する。コミットの実施(素材収集・メッセージ確定・git commit 実行)は commit-flow スキルが担う。9
- 472Diff Reviewyasunori0418/skills「レビューして」「diff をレビュー」「〇〇観点で見て」「PR に出す前にセルフレビュー」などユーザーがコードレビューを依頼したら、観点・レンズ名を挙げていなくても必ず使用する。作業ブランチの diff を複数観点(design / test / yagni、条件付きで spec 等)で並列レビューし統合報告するオーケストレーションスキル。既定は diff 内で完結する fix 指摘のみで、既存コードへの改善提案(リファクタ候補の洗い出し)は起動引数 --improvement の明示時のみ報告する。コードの修正は行わない。9
- 473Gh Fetchyasunori0418/skills非対話セッション(claude-code の remote-control / CI など TTY が無く SSH 鍵パスフレーズを入力できない状況)で git fetch / pull を通すスキル。remote が SSH URL で `ssh -o BatchMode=yes` による非対話 SSH 認証が実際に通る(agent の鍵・パスフレーズ無しのディスク鍵・macOS キーチェーン鍵のいずれでも可)なら素の SSH fetch を実行し、非対話 SSH 認証が通らず `git fetch`/`git pull` が `Permission denied (publickey)` で失敗する場合は、取り込みを HTTPS + gh トークン(credential.helper='!gh auth git-credential')経由へ自動フォールバックして標準入力なしで実行する。「fetch して」「pull して」「リモートの変更を取り込んで」「最新を取ってきて」と頼まれたが SSH 認証が使えない、fetch/pull が publickey で弾かれた、remote-control からリモートの更新を取り込みたい、といった場面で使う。gh-push の取り込み(incoming)版。`/gh-fetch` で明示起動も可。GitHub(gh) 前提。9
- 474Gh Pushyasunori0418/skills非対話セッション(claude-code の remote-control / CI など TTY が無く SSH 鍵パスフレーズを入力できない状況)で git push を通すスキル。remote が SSH URL で `ssh -o BatchMode=yes` による非対話 SSH 認証が実際に通る(agent の鍵・パスフレーズ無しのディスク鍵・macOS キーチェーン鍵のいずれでも可)なら素の SSH push を実行し、非対話 SSH 認証が通らず `git push` が `Permission denied (publickey)` で失敗する場合は、push を HTTPS + gh トークン(credential.helper='!gh auth git-credential')経由へ自動フォールバックして標準入力なしで実行する。「push して」「リモートに反映して」と頼まれたが SSH 認証が使えない、push が publickey で弾かれた、remote-control から push したい、といった場面で使う。`/gh-push` で明示起動も可。GitHub(gh) 前提。9
- 475Githubcellrishi-code/claude-skills-atlasUse GitHub safely through the GitHub CLI (gh). Use when the user asks to inspect a GitHub repository, issue, pull request, branch, commit, workflow run, create or update GitHub content, or open a pull request.5
- 476Nix Devenvyasunori0418/skillsNix + flake-parts 開発環境の構築パターン: root flake.nix(成果物)+ dev/flake.nix(devShell + CI シェル)を direnv で読み込む構成、および GitHub Actions CI テンプレートを提供する。このスキルは /nix-devenv と明示的に呼び出されたときのみ使用する。キーワードマッチによる自動起動はしない。9
- 477Post Merge Cleanupyasunori0418/skillsPR マージ後のローカル後片付け(worktree / ブランチ / tmux セッションの削除と main の最新化)を、収集 → 計画提示 → 承認 → 実行 → 検証のゲートで定型化する。`/post-merge-cleanup [PR番号|ブランチ名]...` の明示実行専用。9
- 478PR Createyasunori0418/skillsPull Request / Merge Request を作成するときに必ず参照する。`gh pr create`/`glab mr create` で PR/MR を作る、コミット済みの作業をレビューに出す、並列・stacked 作業の各ブランチで PR を起こす、といった場面で使う。リポジトリの pull_request_template/merge_request_template を決定論スクリプトで検出して優先し、テンプレの骨組み(見出し・チェックリスト・順序)を改変せず入力箇所を埋めるだけにする(作成前に骨組み照合ゲートで機械検証)。無ければ汎用観点で本文を構成。本文の素材は対象リポジトリの git 差分のみに限定し、他リポジトリ・他タスクの内容を混入させない。draft 既定。head が保護ブランチ(GitHub 上・origin/HEAD の既定ブランチ、main・master・develop・trunk・release 系など)のときだけ push と作成の前にユーザー承認を取り、それ以外は確認せず push して作成する。GitHub(gh) 基本、GitLab(glab) 等にも対応。9
- 479PR Visualizeyasunori0418/skillsGitHub の PR を入力に、変更されたコードやドキュメントを mermaid の図(全体像・関数単位のシーケンス図・参照箇所起点のシーケンス図)で可視化し、短い解説を付けて Markdown ファイルに書き出す。stacked PR では、スタックの全体像と、現在の段を強調した変更の全体像を描く。`/pr-visualize` の明示起動のみ。`--comment` で PR コメントへ投稿(承認必須)。レビューの指摘は行わない。GitHub(gh) 前提。9
- 480Product Namingyasunori0418/skillsプロダクトの役割と目的に合う名前の案を出し、既存のパッケージ・GitHub・同じ分野の製品との重なりを確かめ、比較表で比べて決定を記録するスキル。新しいプロダクトの命名と、既存のプロダクトの改名の検討の両方に使う。/product-naming で明示的に呼び出されたときのみ使用する。9