Comentaris
Comentaris i anotacions del codi
api-and-interface-design
MGallo-Code
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
loom-curator
rjwalters
"Enhances approved issues and prepares them for implementation"
Feature
Atrium-Hermes
Build a feature for every watched repo in one run — iterates the full repo list, picks one feature per repo from yesterday's repo-actions ideas first
git-workflow
pmco23
Use before any destructive git operation (force-push, reset --hard, branch -D, rebase on published commits). Verifies the target, explains the consequences, and requires explicit confirmation. Not needed for routine commits, branch creation, or PRs — those are governed by CLAUDE.md git conventions.
ai-tells
YuukiFST
"Find and remove AI tells in prose: rewrite a draft so it reads like its writer, or audit text for tells without rewriting. Use when text should sound less AI-written or more human, when asked whether writing reads as AI, or when polishing a PR body, commit message, doc, post, or file before it ships. Writing new marketing copy belongs to ai-copywriter."
woostack-address-comments
howarewoo
Use when addressing every unresolved review thread on one exact existing GitHub PR. Verify each concern, make the smallest in-contract fix or evidence-backed pushback, reply, resolve, and read back. Never merges.
mermaid-diagrams
saajunaid
Create software diagrams using Mermaid text-based syntax. Use for class diagrams (domain modeling, OOP design), sequence diagrams (API flows, interactions), flowcharts (processes, algorithms, user journeys), ERD (database schemas), C4 architecture diagrams, state diagrams, git graphs, gantt charts, and data visualization.
baoyu-post-to-x
zqm0779
Posts content and articles to X (Twitter). Supports regular posts with images/videos and X Articles (long-form Markdown). Uses real Chrome with CDP to bypass anti-automation. Use when user asks to "post to X", "tweet", "publish to Twitter", or "share on X".
triage
vaultdex
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
linear
lexijamesesq
Linear reference card — the correct-procedure source for operations where improvising produces wrong results: ticket creation, claiming, state transitions, and structured comment formats. Any agent at any depth invokes it directly; simple reads and basic updates call Linear MCP tools without it. Triggers on "/linear <operation>" or programmatic invocation.
github-issue-generator
ormidales
Analyzes source code sent by the user to generate relevant GitHub issues and create them via the GitHub API. Use this skill as soon as the user sends code (files, snippets, repos) and mentions GitHub, issues, bugs, improvements, or requests a code review. Works with all languages. Generates issues classified as major/minor/patch covering bugs, security, performance, refactoring, documentation, and tests. ALWAYS produce an executable .mjs file as the final output (e.g. create-github-issues.mjs). The .mjs file contains the labels, fully formatted issues with their complete template, and the Node.js code to create them via the GitHub API.
docx
lfalzatel
"Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation."
plan-to-issue
handlename
Use when an implementation plan or design has been finalized in the session and the user wants to record it on GitHub. Either creates a tracking issue (overview + PR-granularity checklist with TASK- IDs) plus a self-contained detailed comment, or — when a related issue already exists (e.g. the plan revises a plan previously posted there) — posts the plan as a self-contained comment on that existing issue, superseding the previous plan comment. Triggers include "issue化して", "計画をissueにして", "turn this plan into an issue", "create a tracking issue for this", "既存のissueにコメントとして投稿して", "計画を issue #N に投稿して".
issuelooper-monitor
kazunori279
"The monitor of this repository's issue loop (issuelooper), for the session whose CC_ROLE is already monitor: the moderator of the whole backlog. Triages every new issue so a worker can claim it, keeps priorities right around the minimum viable product, holds or closes low-value work with a reason, keeps dependencies right, closes stage:live issues once the tester verified them, decides pipeline problems itself, and raises the owner's product decisions at stage:owner. Do not load this to find out what your role is."
commit-guards
vanillagreencom
"Load to add, tune, or debug a commit guard lane, its git hooks, or COMMIT_GUARDS_* settings."
teaching-session
Tzeusy
Teach one concept at a time using Socratic scaffolding and mastery updates.
loom-ci-refusals-reference
rjwalters
"Load when: loom-daemon forge wait-checks printed LOOM-CHECKS-ERROR naming an HTTP 401/403/429, it left a stderr note about legacy commit statuses, or a job needs a re-run (cancelled by a runner shutdown, or flaky)."
shepherd
repairman29
Chump's PR-rescue curator (curator-opus-shepherd role) — execute the shepherd work-your-lane loop. Use to (1) read inbox for shepherd-addressed DMs and operator-paged alerts; (2) run session-start triage (ghost-gap sweep, ambient signature stats, sibling-lease inventory, pickable diff, written game-plan); (3) run a PR-rescue tick (classify BEHIND/BLOCKED/DIRTY PRs and act — rebase, re-arm, file follow-up gap); (4) diagnose a cross-PR failure cluster and broadcast A2A to the owning lane before falling back to a GitHub comment; (5) emit a heartbeat so the orchestrator can audit shepherd liveness. This skill is a thin wrapper over scripts/coord/shepherd-loop.sh (the harness-neutral CLI). Examples that should trigger this skill: "rescue this stuck PR", "run shepherd triage", "unwedge the queue", "why is this PR BEHIND", "heartbeat from shepherd curator".
review-open-issues
CultureBotAI
Sweep and triage the full open-issue queue for CellStructureMech. Fetches every open issue, checks each against main, the corpus, the source queue and the research notes, flags duplicates and already-fixed items, and assigns a priority tier (P0 silently wrong data or a licence breach, P1 real-but-schedulable, P2 process/doc, P3 backlog). Produces a short ranked report; only touches GitHub when asked. Use when asked to "review issues", "prioritize the backlog", "triage open issues", or after a review pass has filed a batch of new issues.
short-video-scripter
lumeierecollection-blip
'Use when the user asks to "script this short video", "write a TikTok / Reels / Shorts script", "给这条抖音或视频号视频写脚本", or "fix the hook — viewers drop off in the first seconds"; produces timestamped beat-sheet scripts on the retention-gate model (0-2s hook / 2-5s confirmation / 5-15s payoff / loop-or-CTA) with per-scene script lines, on-screen text for muted viewing, asset keywords, and 9:16 format-param rows per platform norm card for TikTok, Reels, Shorts, 抖音, and 视频号 — plus 2-3 hook options from named hook families and an AI-content disclosure line by default on realistic synthetic media. Spec-only: rendering, TTS, and publishing stay with the user''s own tools — no pipelines, no upload automation. Not for creator video briefs — use brief-generator; long-form video SEO belongs to content-writer. 短视频脚本/抖音分镜/开头钩子/竖屏9:16'
brn:jira
zfael
Interact with JIRA API for ticket management and tracking. Use when: (1) Listing assigned tickets, (2) Getting details, (3) Updating status.
session-start
lexijamesesq
Triggers when the user says "I'm working on [project]", "Let's work on [project]", "Starting a session on [project]", or similar session-start phrases. Also triggers on "session start" or "/session-start".
Software Engineer
lovits
Write production-ready code with clean architecture, proper error handling, and pragmatic trade-offs between shipping fast and building right.
traffic-cone
lexijamesesq
Correctness layer for lifecycle transitions — verifies tickets are well-formed, receipts are legitimate, and transitions are earned, then executes them directly via the fused script path. Invoked at the point a ticket or map needs to move through claim, begin, mark_done, park, block, un-park, cancel, or close-map.