1. 625Resolve ReviewTalonT-Org/AutoSkillitFetch PR review comments, run intent validation (ACCEPT/REJECT/DISCUSS) before applying fixes, and post inline replies. MCP-only — used exclusively by recipe orchestration via run_skill after review_pr reports changes_requested or needs_human verdict.5
  2. 626Retry WorktreeTalonT-Org/AutoSkillitWorktree retry executor. ALWAYS invoke this skill when instructed to continue or retry an implementation in an existing worktree. Do not resume editing files directly — use this skill first to load the retry workflow.5
  3. 627Review PRTalonT-Org/AutoSkillitAutomated diff-scoped PR code review using parallel audit subagents. Posts inline GitHub review comments and submits a summary verdict. Use after a PR is opened to gate CI on review approval.5
  4. 628Review Research PRTalonT-Org/AutoSkillitAutomated diff-scoped research PR review using parallel audit subagents aligned to research quality dimensions. Posts inline GitHub review comments and submits a summary verdict. Use after a research PR is opened to gate on review approval.5
  5. 629Run ExperimentTalonT-Org/AutoSkillitExecute a designed experiment in a worktree and collect structured results. Supports --adjust retry mode.5
  6. 630Triage IssuesTalonT-Org/AutoSkillitAnalyze open GitHub issues and produce a sequenced implementation plan — grouping issues into parallel batches, ordering those batches, and tagging each issue with its recipe route. Use when user says "triage issues", "prioritize issues", or "plan issue order".5
  7. 631Contributor Experience Reviewpriyank766/OpenSource-SKILLReview of a first-time or early-stage contributor's pull request, where the technical bar stays fixed but the sequencing, batching, and supplied context change. Use when GitHub labels the author a first-time contributor, when the PR comes from a newcomer to this repo, when it arrives via Hacktoberfest, GSoC, Outreachy, or a good-first-issue, when the change is technically close but procedurally messy (missing DCO, wrong base branch, unsigned commits, failing lint), or when the PR must be declined and the decline needs to not cost the project a future contributor. Applies a raised severity floo1
  8. 632Dependency Reviewpriyank766/OpenSource-SKILLSupply-chain review of dependency and CI changes in an open-source pull request. Use when a PR adds or bumps a dependency, changes a lockfile, introduces a build or postinstall script, edits a GitHub Actions workflow, changes a container base image, or when a bot-generated dependency bump needs human judgement before merge. Covers install-time code execution, package-identity and typosquat checks, artifact provenance, transitive footprint, license class, and workflow privilege changes. Ecosystem-agnostic — npm, PyPI, Go, Cargo, RubyGems, Composer, containers. Do NOT use for routine patch bumps1
  9. 633Performance Reviewpriyank766/OpenSource-SKILLPerformance and resource-efficiency review of an open-source pull request or diff. Use when the diff introduces I/O inside a loop, new database queries or query predicates, caching or invalidation changes, large allocations or whole-file reads, changes to a documented hot path, an algorithmic complexity change, a switch between streaming and buffering, or a mix of blocking and async code. Applies a measurement-first rule — every claim must be backed by a benchmark run on both base and head, except complexity-class regressions and unbounded resource growth, which are arguable from the diff alon1
  10. 634PR Reviewpriyank766/OpenSource-SKILLHigh-signal, maintainer-grade review of an open-source pull request. Use when asked to review a PR, review a diff, look over changes before posting feedback, or when preparing review comments for a GitHub pull request. Applies a weighted 10-point quality filter so only findings scoring 8.0+ are surfaced, and enforces a human contributor voice instead of AI cheerleading. Works for any language or ecosystem. Do NOT use for reviewing your own uncommitted work-in-progress.1
  11. 635Commitlucaspmarie-a11y/claude-skills-vaultALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry conventions with proper conventional commit format and issue references. Trigger on any commit, git commit, save changes, or commit message task.5
  12. 636Comprehensive Review PR Enhancelucaspmarie-a11y/claude-skills-vaultGenerate structured PR descriptions from diffs, add review checklists, risk assessments, and test coverage summaries. Use when the user says "write a PR description", "improve this PR", "summarize my changes", "PR review", "pull request", or asks to document a diff for reviewers.5
  13. 637Create PRlucaspmarie-a11y/claude-skills-vaultAlias for sentry-skills:pr-writer. Use when users explicitly ask for "create-pr" or reference the legacy skill name. Redirects to the canonical PR writing workflow.5
  14. 638Creating Github Issues From Web Researchjeremylongshore/claude-code-plugins-plus-skillsThis skill enhances Claude's ability to conduct web research and translate findings into actionable GitHub issues. It automates the process of extracting key information from web search results and formatting it into a well-structured issue, ready for team action. Use this skill when you need to research a topic and create a corresponding GitHub issue for tracking, collaboration, and task management. Trigger this skill by requesting Claude to "research [topic] and create a ticket" or "find [information] and generate a GitHub issue".
  15. 639Generating Conventional Commitsjeremylongshore/claude-code-plugins-plus-skillsGenerates conventional commit messages using AI. It analyzes code changes and suggests a commit message adhering to the conventional commits specification. Use this skill when you need help writing clear, standardized commit messages, especially after making code changes and preparing to commit. Trigger with terms like "create commit", "generate commit message", or "write commit".
  16. 640Generating Smart Commitsjeremylongshore/claude-code-plugins-plus-skillsThis skill generates conventional commit messages using AI analysis of staged Git changes. It automatically determines the commit type (feat, fix, docs, etc.), identifies breaking changes, and formats the message according to conventional commit standards. Use this when asked to create a commit message, write a Git commit, or when the user uses the `/commit-smart` or `/gc` command. It is especially useful after changes have been staged with `git add`.
  17. 641Babysit PRdanybgoode/golden-frijolesAdvisory PR watch for a single open PR — retries flaky CI (re-runs failed workflow runs) and surfaces merge conflicts via one comment; never merges, never a required check. Use when the product owner asks to "babysit this PR", "check on open PRs", "retry flaky CI", "is this PR stuck", "why isn't this PR moving", or as the nightly ops routine's third step (once per open PR across the project's repos). Runs scripts/babysit-pr.mjs, which does the gh reads, the retry, and the comment post. A clean PR (no conflict, no failing checks) gets NO comment — this tool never adds nightly noise to a healthy
  18. 642Build Order Syncdanybgoode/golden-frijolesRegenerates Roadmap/00-ideas/BUILD-ORDER.md when it has drifted from the SSOT (each epic README's frontmatter status:) and opens a claude/ docs PR with the fix — never hand-edits the board. Use when the product owner asks to "sync the build order", "regenerate BUILD-ORDER.md", "check board drift", "is the build-order board stale", "open a build-order PR", or as the nightly ops routine's first step. Runs scripts/build-order-sync.mjs, which does the check, the regen, and (on real drift) the branch/commit/ push/PR — this skill just invokes it and reports the result.
  19. 643Reportdanybgoode/golden-frijolesPosts a project report to a chat destination, at the cadence asked for. Daily: a delta-only standup of overnight signals across every repo the project spans (opened/merged PRs and CI, the latest browser smoke, BUILD-ORDER drift, open-PR state, stale previews). Weekly: an executive recap/retro (merged PRs, shipped epics, deploys per app repo, a retro digest). PMO: the weekly operational report with scrum/DORA/doc-ops metrics and a story deck, or the on-demand monthly stakeholder packet with a metrics sheet. Use when the product owner asks to "post the standup", "run the daily standup", "what ha
  20. 644Brag Doc From Gitagentkitco/agentkit-dev-skillsBuild an evidence-based brag doc or self-review draft from your merged PRs and commits, leaving visible gaps where results are unknown. Use for review season, promotion cases or resumes.
  21. 645Dependency Upgradeagentkitco/agentkit-dev-skillsUpgrade one dependency at a time by reading its changelog, planning for breaking changes, updating code and proving it still builds and passes. Use to bump, update or migrate a package.
  22. 646PR Descriptionagentkitco/agentkit-dev-skillsWrite a pull request title and description from the actual diff and commits, with what changed, why, how it was tested and what to review. Use when asked to write or improve a PR description.
  23. 647Review My Diffagentkitco/agentkit-dev-skillsSelf-review uncommitted or branch changes before a PR, with findings ranked by severity and backed by file and line evidence. Use when asked to review my changes or check my diff.