Loading...
Loading...
Found 2,041 Skills
Use when needing to check PR review comments on current branch, before addressing reviewer feedback, or when asked to fetch/review PR comments
PR triage: audit open PRs, deep review selected ones, draft and post review comments. Args: "all" to review all, PR numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.
Register a repo in the AFK board registry (~/.claude/afk.json) so engineer, triage, and reviewer can resolve its tracker and board. Generates the per-repo entry idempotently with a script, resolving the repo path itself so it works on any machine (laptop, VPS). Use when a repo is not yet on the board ("this repo has no afk.json entry", "set up afk", "register this repo", /afk-setup), or it runs automatically as part of startup.
Read-only triage gate for an autofix chain. Decides whether a tracker issue is a real, still-unfixed defect on the current branch. Stops the chain cleanly with NO_ACTION_NEEDED when the issue is already fixed, already in progress by someone else, already covered by an open PR, or not actually a bug.
Inkblot git branch naming convention. Use when creating a branch, checking out a feature/bugfix branch, naming a PR branch, or when the user asks to start work on a Jira ticket.
Take a PR from review to merged — run the repo's code-review skill on it in a loop (review, fix, re-review) until nothing is left to fix, applying ALL fixes on the PR branch, wait for CI green, then squash-merge. Use when asked to "ship it", "ship PR
Brief a hackathon coach (the platform calls them advisors) on one team, fast. Signs the coach in with the hackathon CLI and picks the event's workspace, then pulls everything about the team, its chat and threads, its help requests and their threads, its demo deck and presentation links, clones or pulls its repository (coaches have read access to every team repository) and summarizes what the team builds, its stack, what it pushed recently, where it is stuck and what it asked. Use when a coach says "brief me on team X", "catch me up on <team>", "what is <team> building", "what are the teams doing", "pull the repo of <team>", "set me up as a coach", or before answering a team's request.
Break a plan into tracer-bullet tickets with blockers and publish via issue-tracker. Local files only if asked.
Propose improvements to a skill in its canonical repository. Defines how to proceed when work does not follow the skill, when information obtained through Web searches differs from or is newer than the skill's content, or when strictly following the skill's conditions is judged to prevent the best possible result. Includes guidance on not directly editing skills installed in the home directory, routing proposals to the appropriate repository, and Issue title and body templates. Use this when you have questions about a skill's content or want to propose an improvement to it.
Add a milestone to an existing project, starting a new milestone cycle, creating the first milestone after project init, or defining what's next after completing work. Triggers include "add milestone", "new milestone", "start milestone", "create milestone", "first milestone", "next milestone", and "milestone cycle".
Agent skill for issue-tracker - invoke with $agent-issue-tracker
Publish and update agent skills on agentskill.sh and skills.sh marketplaces. Covers SKILL.md preparation, submission, verification, and ongoing sync. Use when the user mentions publishing skills, listing on marketplace, updating skill listings, or asks about agentskill.sh or skills.sh.