Comments
Code comments and annotations
spring-boot-scanner
by joaquimscosta
Smart code scanner that detects Spring Boot patterns and routes to appropriate skills. Use when editing Java or Kotlin files in Spring Boot projects, working with pom.xml/build.gradle containing spring-boot-starter, or when context suggests Spring Boot development. Detects annotations (@RestController, @Entity, @EnableWebSecurity, @SpringBootTest) to determine relevant skills and provides contextual guidance. Uses progressive automation - auto-invokes for low-risk patterns (web-api, data, DDD), confirms before loading high-risk skills (security, testing, verify).
merge-check
by medTech-group
Answer "is #12 ready to merge?", "can I merge this?" or "is my change ready?" in the chat, from workflow merge-check --json. "Not yet" gives each reason in plain words and offers the fixes as choices ("Review it now", "Bring it up to date", "Resolve the conflict", "Ask Claude to fix it"); "Ready" gives the try-it link first, then "Merge it now", which checks again on the same head commit and merges with a merge commit pinned to it. Posts nothing on GitHub. Use when someone asks whether a pull request is ready or can be merged, or picks "Check whether #N is ready to merge".
webspec-index
by jnjaeschke
Use webspec-index to query WHATWG, W3C, IETF and TC39 web specifications from the command line
dogfood
by Russ534
"Exploratory QA of web apps: find bugs, evidence, reports."
phpstan-fixer
by marcelorodrigo
Fix PHPStan static analysis errors by adding type annotations and PHPDocs. Use when encountering PHPStan errors, type mismatches, missing type hints, or static analysis failures. Never ignores errors without user approval.
review-panel
by medTech-group
Review a diff or pull request with independent agents in parallel - Standards, Spec, Correctness (with a security review where it applies) and, for UI, API or CLI changes, an explorer that uses the change from outside. Use on any branch or PR, inside build-ticket or alone.
conductor
by medTech-group
Run an unattended build run - ask the owner the run charter's questions once, then hand each ready ticket to its own cloud session, check in on a schedule, keep PRs moving to merge, release as the charter allows, and write the final report. Also resumes or stops a run. Use for "run the backlog unattended", "work over the weekend", "conductor resume", "stop the run".
build-ticket
by medTech-group
Build one ready ticket from claim to merge - tdd at the spec's seams, the review panel in rounds until clean, a pull request with its findings table, CI green, the local suite's evidence, and the merge under the merge rule. Use for "implement #N", "build #N", "build #N with a light review" ("quick build #N"), or a ticket session's briefing.
build-ticket
by medTech-group
Build one ready ticket from claim to merge - tdd at the spec's seams, the review panel in rounds until clean, a pull request with its findings table, CI green, the local suite's evidence, and the merge under the merge rule. Use for "implement #N", "build #N", "build #N with a light review" ("quick build #N"), or a ticket session's briefing.
start
by medTech-group
The guided start - ask what we're working on with clickable choices, split a request into items, propose a path for each (a quick ticket, finding a bug's cause, a spec, a map), record the plan as issues, and offer every next step as a choice, so the person never has to remember a command. Use at the first message of an attended session, on /start, or when the person isn't sure what to do next, and when they say "explain less" or "explain more".
start
by medTech-group
The guided start - ask what we're working on with clickable choices, split a request into items, propose a path for each (a quick ticket, finding a bug's cause, a spec, a map), record the plan as issues, and offer every next step as a choice, so the person never has to remember a command. Use at the first message of an attended session, on /start, or when the person isn't sure what to do next, and when they say "explain less" or "explain more".
coding-standards
by SeuPut0705
Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns. Use when reviewing code quality or naming with no framework-specific skill that applies.
merge-check
by medTech-group
Answer "is #12 ready to merge?", "can I merge this?" or "is my change ready?" in the chat, from workflow merge-check --json. "Not yet" gives each reason in plain words and offers the fixes as choices ("Review it now", "Bring it up to date", "Resolve the conflict", "Ask Claude to fix it"); "Ready" gives the try-it link first, then "Merge it now", which checks again on the same head commit and merges with a merge commit pinned to it. Posts nothing on GitHub. Use when someone asks whether a pull request is ready or can be merged, or picks "Check whether #N is ready to merge".
update-markdown-file-index
by boi6765
'Update a markdown file section with an index/table of files from a specified folder.'
run-report
by medTech-group
Write the final report of an unattended run (or a progress report mid-run) - what merged, what was set aside and why, what's live, the outward changes to confirm or undo, the decisions for the owner, the by-hand checks and the follow-ups. Used by the conductor at the end of a run, or alone.
fable
by mickeyyaya
Use when running any LLM agent below Fable 5 — Claude (Opus/Sonnet/Haiku), GPT via codex, Gemini via agy, or local models via ollama — to adopt Fable 5's operating discipline — evidence-first investigation, premise verification, root-cause-only fixes, adversarial self-review, calibrated autonomy, and honest failure reporting. Load at session start or as a persona overlay for phase agents on any CLI.
explain-visually
by dcouple
Complement an answer or discussion with a first-principles visual HTML explanation, saved in Grain when connected. Use when explaining how something works, why it changes, or how options differ and a visual would materially help understanding, including requests like "show me" or "help me understand." Skip simple factual answers and text-only requests.
notion-cli
by adbertram
Use this skill for service operations only. DO NOT use this skill for CLI implementation lifecycle work such as creating, testing, updating, troubleshooting, validating, removing, or documenting the CLI tool itself; delegate those tasks to cli-tool-expert. Execute Notion operations using the notion CLI tool. CLI interface for Notion API with database query filtering. Triggers: notion, notion cli, notion databases, notion pages, notion comments, notion fields, notion users, notion mention, mention someone in notion, notify notion user, list notion databases, search notion pages, query notion database, create notion page, update notion page, export notion page, download notion page files, download notion skills, notion page content, notion blocks, notion schema, notion templates
python-types-contracts
by ahgraber
Use when defining or evolving public interfaces, schema boundaries, or pydantic usage in Python. Also use when annotations are missing on public APIs, pydantic models appear everywhere instead of at trust boundaries, contract changes lack migration guidance, or Any/object types are overused across module boundaries.
hyvor-cli
by adbertram
Use this skill for service operations only. DO NOT use this skill for CLI implementation lifecycle work such as creating, testing, updating, troubleshooting, validating, removing, or documenting the CLI tool itself; delegate those tasks to cli-tool-expert. Execute hyvor operations using the hyvor CLI tool. CLI interface for Hyvor Talk API -- manage blog comments, moderate spam, reply to comments, and handle profiles. Triggers: hyvor, hyvor cli, hyvor comments, hyvor talk, list hyvor comments, reply to comment, moderate comments, hyvor spam, pending comments, publish comment
podio-cli
by adbertram
Use this skill for service operations only. DO NOT use this skill for CLI implementation lifecycle work such as creating, testing, updating, troubleshooting, validating, removing, or documenting the CLI tool itself; delegate those tasks to cli-tool-expert. Execute podio operations using the podio CLI tool. CLI interface for Podio API - Manage apps, items, tasks, and more. Triggers: podio, podio cli, podio items, podio apps, podio tasks, list podio items, podio workspace, podio conversations, podio files, podio webhooks, my podio
coding-standards-common
by exception-coder
Use when writing, reviewing, or modifying source code in any language. Provides cross-language rules for structure, naming, scope, errors, duplication, testing, and comments.
pr-test-automation
by dcouple
Run first-pass automated manual testing for PRs that are reviewed or nearly ready to merge. Use when the user asks Codex to test a PR/branch/worktree, validate product flows, exercise browser or CLI workflows, map changed UI journeys with screenshots, verify analytics/webhooks/payments/email/SMS behavior through connected tools, or produce manual QA notes before human testing.
engineering-craft
by mickeyyaya
Use when writing or changing any production code or tests — new features, bug fixes, refactors, or test authoring, in any language, by any model on any CLI.