aantoniadis/skills

check-acceptance

Checks delivered code against a set of requirements — GitHub issues, an epic, Jira or Linear tickets, a spec or plan, or pasted text — and reports which are met, partly met, unmet, unverified, or unclear, with evidence; also delivered behavior nobody asked…

원문 언어: 영어

find-bugs

Finds the defects in a change (a PR, a branch, or the working tree) that a maintainer would fix, with evidence from inspected source or executed probes. Use when the user asks to find bugs, review a diff for defects, or check a change before it merges or…

원문 언어: 영어

fix-bug

Finds the cause of a reported bug and fixes or diagnoses it, with a demonstrated reproduction, a regression test that went red then green, and a diagnosis note with an HTML page a reviewer can verify. Use when a test or CI job fails, an issue reports wrong…

원문 언어: 영어

pr-review-guide

Writes the guide a human reviewer needs for a pull request, against a pinned snapshot: what the change means, where to pay attention, what to ask the author, and a search for bugs when selected, then answers follow-up questions on the same report. Use when…

원문 언어: 영어

setup-tools

Discovers, checks, and prepares a project's tools (tests, search, symbol navigation, coverage, browser, report checker, the installed Matt Pocock and HumanLayer skills) before investigation or review work, and repairs a stale local tool record. Use when…

원문 언어: 영어

explain

Explains how existing code behaves for one question or feature, tracing a concrete flow to pinned source lines, with a reusable note or HTML page when selected. Use when the user asks how something works, wants a flow traced, needs onboarding to an area of a…

원문 언어: 영어

plan-change

Plans an engineering change, or reviews an existing plan, for indirect behavior changes and consequential assumptions, and drafts specs and tickets when selected. Use when a ticket or request is vague, when a change has consequences beyond its own function,…

원문 언어: 영어