aantoniadis/skills

aantoniadis のプロフィール

記録された最新のソース活動: 2026年10月20日 15:47

SkillsMP カタログ更新: 2026年10月26日 11:37

収集済み skills: 7

GitHub スター: 0
GitHub フォーク: 0

リポジトリの README

README の元ファイル：README.md

README の元ファイルを読む

README 全文を表示

# skills Skills for coding agents, shipped as the **`aantoniadis-skills`** plugin for Claude Code, Codex, and OpenCode. Seven skills cover the work around a change: set a project up for evidence, understand the code, plan the behavior, fix a reported bug, find the defects, review the PR, and check delivered work against its requirements. Matt Pocock's and HumanLayer's originals, installed separately, carry a plan through spec, tickets, implementation, and the PR. ```bash claude plugin marketplace add aantoniadis/skills && claude plugin install aantoniadis-skills@aantoniadis ``` Invoke a skill as `/aantoniadis-skills:<name>` in Claude Code, `$aantoniadis-skills:<name>` in Codex, and through the `/skills` menu or `opencode run --command <name>` in OpenCode. Hosts also pick the skills up through their normal model-driven selection. ## Install ```bash # Claude Code claude plugin marketplace add aantoniadis/skills claude plugin install aantoniadis-skills@aantoniadis # Codex codex plugin marketplace add aantoniadis/skills codex plugin add aantoniadis-skills@aantoniadis ``` The skills run Python 3 scripts. The page checker and renderer need two packages; HTML pages with diagrams also use Node.js ([renderer options](skills/RENDERER.md)). `setup-tools` installs the packages into a private environment that the checker finds on its own; to do it yourself: ```bash v="${XDG_STATE_HOME:-$HOME/.local/state}/aantoniadis-skills/venv"; python3 -m venv "$v" && "$v/bin/python3" -m pip install -q markdown-it-py beautifulsoup4 ``` OpenCode loads the plugin from `opencode.json`, from Git or from a checkout: ```json { "plugin": ["@aantoniadis/skills@git+https://github.com/aantoniadis/skills.git"] } ``` ```json { "plugin": ["/path/to/skills/opencode/skills.js"] } ``` Start a new session after an install or update. **Updates.** Every merge to the default branch is a release. Codex reinstalls the plugin when it starts on new commits. Claude Code updates by hand, or on its own once auto-update is on for the `aantoniadis` marketplace under `/plugin`: ```bash claude plugin marketplace update aantoniadis && claude plugin update aantoniadis-skills@aantoniadis ``` OpenCode caches a Git-installed plugin; delete `~/.cache/opencode/packages/@aantoniadis` to fetch the current version. A checkout updates with `git pull`. For development, `claude --plugin-dir <checkout>` runs the checkout directly. ### Original skills Our skills work with six originals: Matt Pocock's `grilling`, `to-spec`, `to-tickets`, and `implement`, and HumanLayer's `show-me` and `visual-pr`. Install them once per machine, one route per host: ```bash # Matt Pocock's skills: Claude Code claude plugin install mattpocock-skills@claude-plugins-official # Matt Pocock's skills: Codex codex plugin marketplace add mattpocock/skills codex plugin add mattpocock-skills@mattpocock # Matt Pocock's skills: OpenCode and other hosts (-a <agent> selects the host) npx skills@latest add mattpocock/skills -g # HumanLayer's skills: every host npx skills@latest add humanlayer/skills --skill show-me --skill visual-pr -g ``` `setup-tools` records where each copy is. Our skills name them `mattpocock:implement` or `humanlayer:visual-pr` ([skills/REFERENCES.md](skills/REFERENCES.md)) and respect each author's choice of who runs it: `plan-change` invokes `grilling` through the host; the other five are user-invoked, so our skills finish their own deliverable and hand you the command, such as `/mattpocock-skills:to-spec` in Claude Code or `/to-spec` after an `npx skills` install. Each original then runs its own workflow, unchanged. ## The skills | Skill | Use it when | You get | How it works | | --- | --- | --- | --- | | [`setup-tools`](skills/setup-tools/SKILL.md) | Reusable preparation or repair would help the intended work | Useful tools checked, with a local untracked record when there is preparation to retain | [docs/setup-tools.md](docs/setup-tools.md) | | [`explain`](skills/explain/SKILL.md) | You need to know how a flow works before touching it | A source-cited answer, with a reusable note or HTML page when selected | [docs/explain.md](docs/explain.md) | | [`plan-change`](skills/plan-change/SKILL.md) | A ticket is vague and the change has consequences beyond its own function | A plan with named decisions, preserved behavior, evidence, and acceptance scenarios | [docs/plan-change.md](docs/plan-change.md) | | [`find-bugs`](skills/find-bugs/SKILL.md) | You want the defects in a change before it merges, or before you review it | Ranked defects with evidence, material questions, and review limits | [docs/find-bugs.md](docs/find-bugs.md) | | [`fix-bug`](skills/fix-bug/SKILL.md) | A test fails, an issue reports wrong behavior, or production shows a symptom | A demonstrated cause, a fix with a regression test that went red then green, and a diagnosis page a reviewer can verify | [docs/fix-bug.md](docs/fix-bug.md) | | [`pr-review-guide`](skills/pr-review-guide/SKILL.md) | You have to review a PR you did not write | A guide to a pinned snapshot: what the change means, where to look, what to skim, what to ask the author | [docs/pr-review-guide.md](docs/pr-review-guide.md) | | [`check-acceptance`](skills/check-acceptance/SKILL.md) | You need to know whether a set of issues, an epic, tickets, or a spec is delivered | Per-requirement status at a pinned revision with evidence, delivered behavior nobody asked for, and a search for bugs when selected | [docs/check-acceptance.md](docs/check-acceptance.md) | The skills start from context and settled choices, and ask only about open preferences or consequential decisions. Every claim sits next to its evidence: a pinned line, an executed check, a quote, or a label such as inferred or not inspected. `setup-tools` keeps what it learns in a [local record](skills/TOOL-SETUP.md) outside the repository. With the originals: `plan-change` hands agreed decisions to Matt's `to-spec` and `to-tickets`, Matt's `implement` builds an unblocked ticket, `fix-bug` takes a reported symptom to a fixed, recorded cause, `find-bugs` runs before HumanLayer's `visual-pr` opens the PR, `pr-review-guide` serves the PR's human reviewer, and `check-acceptance` checks the built result against the requirements across a set of issues. An original you run keeps its own behavior, such as committing or pushing, including after one of our handoffs; `grilling`, which `plan-change` invokes, works within that skill's scope. - [Using the skills together](docs/workflow.md): copyable prompts, project setup, handoffs, and artifact locations - [The light path](docs/light-path.md): a shorter workflow for contained changes in familiar code ## License [MIT](LICENSE). Bundled third-party assets, the Manrope font and highlight.js, keep their own licenses; [THIRD-PARTY-NOTICES.md](THIRD-PARTY-NOTICES.md) lists them.

リポジトリの README を読み込んでいます…

このリポジトリの skills

分類待ち

skill

職業分類

説明

更新

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…

原文の言語: 英語

2026-10-20

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…

原文の言語: 英語

2026-10-20

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…

原文の言語: 英語

2026-10-20

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…

原文の言語: 英語

2026-10-20

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…

原文の言語: 英語

2026-10-20

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…

原文の言語: 英語

2026-10-13

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,…

原文の言語: 英語

2026-10-13

収集済み skill 7 件中 7 件を表示しています。

AI アシスタントでインストール

このプロンプトをコピーして、使用中の AI アシスタントに送ってください。

Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/aantoniadis/skills.