#SkillRepo stars
- 289Fix Issuehw-native-sys/simplerImplement a GitHub Issue as its assignee or delegated contributor, selecting direct repair or develop-task planning and following through to a reviewed PR. Use when asked to fix or work on an Issue; use process-issue for maintainer triage.49
- 290Fix PRhw-native-sys/simplerFix GitHub PR issues — address all PR feedback (inline review threads, review summary bodies, and conversation comments) and resolve CI failures in a loop until the PR is fully clean. Fetches CI errors online and triages review feedback. Use when fixing PR problems, addressing review comments, or resolving CI failures.49
- 291Git Commithw-native-sys/simplerComplete git commit workflow including pre-commit review, staging, message generation, and verification. Use when creating commits or preparing changes for commit.49
- 292Github PRhw-native-sys/simplerCreate or update a GitHub pull request after committing, rebasing, and pushing changes. Use when the user asks to create a PR, submit changes for review, or open a pull request.49
- 293Maintainerhw-native-sys/simplerMaintain GitHub Issues and PRs through an action table, focused user decisions and recurring monitoring or a requested single pass. Use for repository, Issue, track or personal scopes, optionally filtering PR target branches. Scope does not grant repository authority; continuous monitoring requires a working wake mechanism.49
- 294Multi Repo Dsv4flash Setuphw-native-sys/simplerConcrete guide to benchmark DeepSeek-V4 (dsv4) FLASH on NPU against the current worktree's simpler — the three decode attentions (swa/csa/hca) and the distributed MoE, all in pypto-lib's models/deepseek/v4/. Defers cross-repo clone/install to multi-repo-setup, then gives the exact PYPTO_BENCH run commands and the hard-won config that makes the numbers reproducible: pin ptoas 0.48 (0.50/ptoas-bin cannot compile csa), pin --start-pos 8192, edit moe.py for 16 experts/card, read fast_effective_us not effective_us, pin an even die, and apply the eager-init idempotency guard so distributed MoE runs 49
- 295Multi Repo Qwen Setuphw-native-sys/simplerConcrete qwen3-14B guide on NPU against the current worktree's simpler. Points at simpler's own in-repo qwen3_14b_decode example (zero cross-repo), then covers the two cross-repo paths — the pypto-serving runner (prefill/decode TPOT) and the pypto-lib decode_fwd kernel (device decode TPOT + scheduler DFX). Defers cross-repo clone/install to multi-repo-setup, then gives the exact run commands (batch-1 and batch-16), the prefill ring/timeout gotchas that otherwise surface as 507018, how to read the per-token timing layers, and the kernel-level device-timing / swimlane flow. Invoke when running q49
- 296Multi Repo Setuphw-native-sys/simplerSet up a cross-repo investigation when a workload from another repo (pypto, pypto-lib, pypto-serving, etc.) needs to be run, especially when you want to swap in simpler-main HEAD or the current worktree's simpler instead of the version that repo pins. Documents the repo graph (who imports who), clones-or-updates each external repo every invocation so stale local clones don't lie about CI parity, and points at each repo's own skills/docs for workload-specific steps. MUST invoke before chasing "X doesn't work on simpler" reports where X lives outside this repo.49
- 297Process Issuehw-native-sys/simplerProcess a GitHub Issue as a maintainer, from triage and ownership routing through dependencies and evidence-based closure. Use to manage an Issue's next step; use fix-issue for implementation.49
- 298Process PRhw-native-sys/simplerProcess a GitHub PR as a maintainer, routing review, following revisions, checking merge readiness and reconciling linked Issues. Use for PR lifecycle management; use review-pr for technical review and fix-pr for author-side repairs.49
- 299Review PRhw-native-sys/simplerReview a GitHub PR or a fixed commit range from its background, existing pain points, and expected benefits through correctness, architecture, decoupling, performance, code quality, and repository standards. Uses the correct diff (fixed range or merge-base) and checks claims against implementation and evidence. Optionally folds in independent reviews from local `codex` / `claude` CLIs or read-only sub-agents when the invocation explicitly opts in. Use when the user asks to review a PR, a fixed range, or changes.49
- 300Vicious MockeryHmbown/Wizards-of-the-GhostsThe bard's cantrip that deals psychic damage through insults. In practice this is adversarial review — the art of finding and articulating exactly what is wrong with something in a way that is impossible to ignore. Unlike polite feedback that gets filed and forgotten, vicious mockery lands. It is the red-team report that makes the PM cancel the launch, the code review that makes the author delete the PR, the roast that makes the founder pivot. The damage is the point.113
- 301Weekly Changeloghw-native-sys/simplerSummarize user-facing changes merged in the current Friday-anchored week (most recent Friday up through yesterday) in the simpler repo into a markdown changelog with before/after code examples. Also emits a full all-PR inventory (WEEKLY_ALL_PRS) and Chinese (_zh) translations of both docs. Use when the user asks for a weekly changelog, weekly summary, or weekly external changes report.49
- 302Fix Issuesmartwhale8/claude-playbookResolve a GitHub issue end to end, from reading the issue through to opening a pull request. Use when the user names an issue number to fix.44
- 303Review PRsmartwhale8/claude-playbookReview a pull request for correctness, architecture, security, and test coverage. Use when the user names a PR number to review.44
- 304Regel Checkneubauerwilli/gta6-skillDer Regel-Check. Prüft jeden Clip gegen die Regeln der Kampagne (Länge, Wasserzeichen, Pflicht-Tags, Erwähnung, Plattform, Frist), bevor er rausgeht. Nutze ihn immer vor dem Posten, oder wenn der Nutzer sagt "prüf den Clip", "darf ich das posten", "Regeln checken" oder "ist der Clip okay".51
- 305Git Workflowjefflester/claude-skills-superchargedGit workflow best practices including commit messages, branching strategies, pull requests, and collaboration patterns. Use when working with Git version control.43
- 306PR Descriptionpetekp/claude-code-setupWrite or update a GitHub PR description a teammate understands in one quick read: clear before/after behavior, useful visual evidence, and plain sentences grounded in the diff and real verification. Use when opening a PR or editing its description.49
- 307PR Screenshot Comparisonpetekp/claude-code-setupCreate clear, polished before-and-after screenshots from the actual running product for a GitHub pull request. Use when a UI change needs visual proof: capture matching product states, crop to the relevant UI, stitch and caption one comparison image, attach it natively to the PR, and keep the image out of the repository.49
- 308PR Self Reviewpetekp/claude-code-setupDraft explanatory author-context comments for the user's own PR or local diff. Use for self-review or reviewer context, not a formal review submission. Posting requires approval.49
- 309Finishing a Development Branchsodiumjoe/dotfilesUse when implementation is complete, all tests pass, and you need to decide how to integrate the work49
- 310Neovim Reviewsodiumjoe/dotfilesUse when the user invokes /neovim-review for a pull request or a local :Review session in Neovim.49
- 311Secrets Management Auditmn-youssef/security-skillsUse when hunting for exposed secrets and auditing how an app you own manages them — API keys, tokens, passwords, and private keys in source, git history, binaries, logs, config, and CI; plus vaulting, rotation, and least-privilege of the secrets themselves.49
- 312Uw Unity Project Setupdevdavv/unity-ai-workflowFull project initialization wizard from ProjectConfig, including folders, packages, Git, and MCP setup. Use when setting up a new Unity project from scratch, creating the folder structure, or bootstrapping infrastructure. Triggers on requests like "set up a new project", "create folder structure", "initialize the project", or "/uw-cmd-setup-project". Reads ProjectConfig.yaml for all decisions.47
- 313Historylis186/SourceAtlasSmart temporal analysis using git history - Hotspots, Coupling, and Recent Contributors49
- 314Ijfw CommitFerroxLabs/wayland-coreTerse conventional commits. Trigger: commit, git commit, /ijfw-commit43
- 315Careful DeleteElliotJLT/Claude-Skill-PotionsBefore any destructive or irreversible operation (rm -rf, DROP TABLE, DELETE, force push, branch deletion, truncate), orchestrate a safety cycle: assess blast radius → confirm explicitly → document what happened. Chains pre-mortem and you-sure with built-in documentation. No dangerous operation executes without ceremony.62
- 316Code Review Receptionobra/clankReceive and act on code review feedback with technical rigor, not performative agreement or blind implementation43
- 317Contributeinite-ai/inite-brain-serviceTake an idea for INITE Brain from plain words to a green pull request. Use when someone says "I have an idea", "I want to add / change / fix something in Brain", "make Brain do X", or asks how to contribute — engineer or not.43
- 318Finishing a Development Branchobra/clankComplete feature development with structured options for merge, PR, or cleanup43
- 319Spec Ideainite-ai/inite-brain-serviceTurn an idea for INITE Brain into a well-formed GitHub issue — no code. Use when someone wants to propose, suggest or request something for Brain ("it would be great if Brain…", "can you file this idea") but not build it themselves.43
- 320Using Git Worktreesobra/clankCreate isolated git worktrees with smart directory selection and safety verification43
- 321Diff Intakeamplitude/mcp-marketplaceReads a PR or branch diff and produces a structured YAML change brief for downstream analytics instrumentation skills. Use this as the first step whenever a user shares a PR link, branch comparison, or raw diff and wants to understand what changed, what needs tracking, or how to instrument a feature. Trigger on phrases like "review this PR", "what changed in this branch", "help me instrument this diff", "check analytics coverage for this change", or any request to start the analytics review workflow.48
- 322Distributed MeshAzure-Samples/agent-skills-dotnet-demoHow to coordinate with squads on different machines using git as transport45
- 323Gh Auth IsolationAzure-Samples/agent-skills-dotnet-demoSafely manage multiple GitHub identities (EMU + personal) in agent workflows45
- 324Git WorkflowAzure-Samples/agent-skills-dotnet-demoSquad branching model: dev-first workflow with insiders preview channel45
- 325Github Multi AccountAzure-Samples/agent-skills-dotnet-demoDetect and set up account-locked gh aliases for multi-account GitHub. The AI reads this skill, detects accounts, asks the user which is personal/work, and runs the setup automatically.45
- 326Whose Redokgrit/done-is-a-claimInvestigate whether a failing test run is caused by a change, was already broken on main, or is inconclusive, using matched branch and clean-main runs. Use when tests fail on a branch or PR, when an agent says 'this failure is pre-existing', or before retrying or reverting a fix.33
- 327Changelogratacat/claude-skillsCreate engaging changelogs for recent merges to main branch59
- 328Git History Analyzerratacat/claude-skillsUse this agent when you need to understand the historical context and evolution of code changes, trace the origins of specific code patterns, identify key contributors and their expertise areas, or analyze patterns in commit history. This agent excels at archaeological analysis of git repositories to provide insights about code evolution and development patterns. <example>Context: The user wants to understand the history and evolution of recently modified files.\ user: "I've just refactored the authentication module. Can you analyze the historical context?"\ assistant: "I'll use the git-histor59
- 329Git Worktreeratacat/claude-skillsThis skill manages Git worktrees for isolated parallel development. It handles creating, listing, switching, and cleaning up worktrees with a simple interactive interface, following KISS principles.59
- 330PR Comment Resolverratacat/claude-skillsUse this agent when you need to address comments on pull requests or code reviews by making the requested changes and reporting back on the resolution. This agent handles the full workflow of understanding the comment, implementing the fix, and providing a clear summary of what was done. <example>Context: A reviewer has left a comment on a pull request asking for a specific change to be made.user: "The reviewer commented that we should add error handling to the payment processing method"assistant: "I'll use the pr-comment-resolver agent to address this comment by implementing the error handlin59
- 331Shepherdrobinebers/skillsShepherd a GitHub pull request all the way to merge-ready by relentlessly polling status and only acting once all automatic reviewers have finished. NEVER merges without explicit human approval. Use when the user says things like "shepherd this PR", "babysit this PR", "get this PR merge-ready", "wait for Cubic", "wait for Bugbot", or asks to drive a PR through review.49
- 332Worktree Setuprobinebers/skillsGenerate setup scripts/configs for AI agent worktrees and isolated environments across Cursor, Codex, Conductor, and Claude Code. Use when wiring up a project so AI agents start with the same dependencies, env files, and tool configs as the main repo.49
- 333Meshtastic Org Knowledgemeshtastic/meshtastic-mcpFind and answer questions across all Meshtastic GitHub repos — what projects exist, what their docs say, their current status (releases, open PRs/issues, recent commits), and how they relate. Use when a question spans more than one repo, or asks "which project does X", "what's the status of Y", "where is Z documented", or "what changed recently across the org".23
- 334Trellis Mvp to Delivery Zhcoldwateryi/trellis-skills根据源需求文档审计已有 MVP,并执行 Trellis 完整交付 loop 的审计、状态维护、批次规划和最终验收。用于 Codex 被要求在 MVP 后继续、补齐剩余需求、执行 full/delta 差距审计、维护 Requirements Traceability Matrix、分类 DONE/PARTIAL/MISSING/UNTESTED/UNCLEAR 条目、初始化或更新 .trellis/delivery-state.md、规划有边界的补缺批次、要求 worktree + verifier 门、设计自动化测试覆盖、分类发现的 bug,或在交付前执行最终验收的场景。若由 trellis-delivery-controller-zh 调用,则遵循控制器已选定的 loop 模式和审计范围;若单独调用,则按本技能的 delivery-loop-policy 自行判定。44
- 335Trellis Skill Assimilatorcoldwateryi/trellis-skillsExtract reusable engineering capabilities from external GitHub skill projects and produce safe Trellis absorption plans. Use when the user provides a GitHub repository URL, skill project URL, open-source agent skill collection, or asks to compare or update projects such as superpowers, gsd, CodeStable, loop-engineering, ponytail, or similar. Analyze README/SKILL.md/references/scripts/license and produce source analysis, capability extraction, absorption card, Trellis target mapping, risk judgment, update-scan delta report, and verification scenario recommendations. Do not copy third-party skil44
- 336Trellis Skill Assimilator Zhcoldwateryi/trellis-skills从外部 GitHub skill 项目中提取可复用工程能力,并按 Trellis skills 架构进行安全吸收规划。用于用户提供 GitHub 仓库地址、skill 项目地址、开源 agent skill 集合、或要求比较 superpowers、gsd、CodeStable、loop-engineering、ponytail 等项目更新时,分析 README/SKILL.md/references/scripts/license,生成 source analysis、capability extraction、absorption card、Trellis 落点、风险判断、update-scan delta 报告和验证场景建议。不要直接复制第三方 skill 原文;只吸收能力模式、流程结构和可验证设计。44