Comentaris
Comentaris i anotacions del codi
dotfiles-research-methodology
taloncjones
Use when turning a hunch, idea, or half-diagnosed problem in this dotfiles repo into an accepted change -- when you are about to say "I think the cause is X", propose a new subsystem, or decide whether an experiment "worked". Trigger phrases -- "I have a theory", "should we build/add/try X", "is this fix real", "the test passed so we're done", "let's just remove it". Covers the evidence bar (one mechanism explains ALL observations), predict-before-run, the idea lifecycle (adopted AND retired both count as success), and where good ideas historically came from. NOT for executing an already-approved change (dotfiles-change-control), triaging a live failure (dotfiles-debugging-playbook), looking up a settled past investigation (dotfiles-failure-archaeology), or picking a new open problem to work on (dotfiles-research-frontier).
mybatis-patterns
SeuPut0705
MyBatis and MyBatis-Spring patterns for mapper design, XML and annotation SQL, result mapping, dynamic SQL safety, transactions, batching, pagination, and query performance. Use when building or reviewing Java persistence code with MyBatis, Spring Boot, MyBatis-Spring, or MyBatis-based legacy applications.
stack-decomposition-format
KingInYellows
'Structured format contract for "## Stack Decomposition" sections in plan documents, shared by gt-stack-plan (producer) and flow:work (consumer). Use when writing or parsing a Stack Decomposition section.'
post-merge
taloncjones
Use after a PR is merged to tear down its worktree/branch and sync its Jira ticket. Removes the merged branch's git worktree (handling submodule-bearing worktrees), deletes the local + lingering remote branch, sweeps co-review leftovers, then transitions the linked Jira issue to Done, assigns it to me, adds it to the current sprint, sets its epic, and posts a resolution comment. Finally distills tagged agent lessons into
ce-debug
KingInYellows
'Systematically find root causes and fix bugs. Use when debugging errors, investigating test failures, reproducing bugs from issue trackers (GitHub, Linear, Jira), or when stuck on a problem after failed fix attempts. Also use when the user says ''debug this'', ''why is this failing'', ''fix this bug'', ''trace this error'', or pastes stack traces, error messages, or issue references.'
ship
taloncjones
Use when a branch or PR is implementation-complete and the user wants it taken through the explicit merge gate and cleanup.
issuelooper-shared
kazunori279
"Shared reference for this repository's issue loop (issuelooper): the roles (worker, merger, tester, monitor, aide), how the supervisor ccpool.py runs them, the label scheme and who may set what, the merge gates a pull request must pass, comment signing, and the limits every session works under. Read it first, then .issuelooper/project.md, then the skill for your CC_ROLE."
issuelooper-tester
kazunori279
"The tester of this repository's issue loop (issuelooper), for a session whose CC_ROLE is already tester. Two units: the live check of one stage:live issue against the live environment, and the UX run, which walks the deployed app the way a person would (desktop and phone, every language the app offers, screenshots while work is in progress, scrolling, reload), reads every screenshot together against the spec as a harsh UX reviewer, and files at most five new findings; and, when the workers have nothing to do, the spec check, which tests the app against the spec one requirement at a time. Do not load this to find out what your role is."
automated-instagram-dm-sales-funnel-voice-personalization
Eitanvinokur12345
"Automate selling courses, communities, and agency services via Instagram DMs using comment triggers and AI voice agents."
herdr-vues
remmmi
Ouvrir à côté de la session, dans un pane herdr (ou tmux), ce que l'utilisateur doit SAISIR, LIRE ou VOIR VIVRE, au lieu de le mettre dans le chat. Invoquer SANS attendre qu'on le demande dès que : il faut un secret (mot de passe, jeton, clé, htpasswd) → jamais dans le chat ; l'utilisateur doit coller un résultat venu d'ailleurs (relevé d'un autre outil, export) ; un texte de plus de ~15 lignes est à relire ou corriger (brouillon de mail, d'issue, de PR, réponse à envoyer, doc, texte et son décodage) ; une commande longue ou un log à suivre (deploy, import, tests, tail -f, watch, sous-agent). Aussi sur « montre-moi en entier », « affiche », « ouvre dans nano », « ouvre en pane », « pane token », « je veux voir », « surveille », « ferme les panes ». Outil : commande vue.
explain-algorand-x402-python
algorand-devrel
Explain the x402-avm Python package for Algorand payment protocol integration. Use when developers ask about x402 Python package structure, extras installation ([avm], [evm], [svm], [fastapi], [flask], [httpx], [requests], [all]), signer protocols (ClientAvmSigner, FacilitatorAvmSigner), async vs sync variants, registration patterns, or algosdk encoding boundaries. Strong triggers include "how does x402 work in Python?", "explain x402-avm Python package", "what extras do I install?", "ClientAvmSigner vs FacilitatorAvmSigner", "algosdk encoding in x402", "async vs sync x402 Python", "how do I sign Algorand transactions in x402?", "msgpack_decode expects base64".
anndata
ovachiever
This skill should be used when working with annotated data matrices in Python, particularly for single-cell genomics analysis, managing experimental measurements with metadata, or handling large-scale biological datasets. Use when tasks involve AnnData objects, h5ad files, single-cell RNA-seq data, or integration with scanpy/scverse tools.
wicked-garden-qe-coverage-archaeologist
mikeparcewski
Find dark corners in legacy code — untested, unreferenced, or low-confidence paths. Prioritizes by risk using coverage + git history + call-graph. Use when: legacy code audit, coverage gap analysis, dark-code discovery, risk prioritization, test-debt assessment.
wicked-garden-engineering-docs
mikeparcewski
Use when generating documentation from code, auditing documentation coverage for gaps, or detecting code-doc drift after a refactor. Covers generate (API docs, READMEs), audit (coverage metrics, undocumented exports), and sync (stale docs detection) in one skill. NOT for architecture documentation (use the architecture skill) or product requirements (use product/requirements-analysis).
wicked-garden-domain-coverage
mikeparcewski
Coverage evaluator + pre-build threat model for the domain-extraction workflow (CONTRACT-3 §2). Emits coverage-report.json from the estate store, then adversarially reviews the extracted domain model: hunts missing error paths, ungrounded rules, reason-less drops, cross-cluster smears, and coverage holes. Use when: dispatched as the coverage phase of a domain-extraction workflow run. The phase runs in a git worktree; WICKED_ESTATE_DB points at the live estate store. NOT for mining rules (domain-extractor) or grouping domains (domain-modeler). This worker EMITS coverage evidence AND CRITIQUES the domain model.
wicked-garden-domain-extractor
mikeparcewski
Rule-extraction worker for the FOUNDATIONAL domain-model capability. Mines testable business rules from a codebase — each with a numeric confidence and a provenance{source, ref, source_kinds} — and annotates them into the estate store so wicked-core can build the domain-model requirements graph (coverage-gated). This is a substrate, not a modernization tool: the modernize archetype DERIVES from it, and build / migrate / review / specify / explore can consume the same domain model — none OWN it. Use when: dispatched by wicked-garden-domain to mine the business_rules of a codebase (or a module); "extract the domain rules", "what does this system require", building the requirements half of a domain model. NOT for grouping into domains (that is domain-modeler) or judging coverage (that is domain-coverage — a seat-distinct evaluator).
wicked-garden-domain
mikeparcewski
The FOUNDATIONAL domain-model capability: extract a codebase's domain — testable business rules (with confidence + provenance), entities, requirements — as a schema-conformant model on the estate graph. The workers annotate the store; wicked-core reads it and builds the requirements graph, coverage-gating fail-closed. Steers three workers. A shared substrate, not a modernization tool. The modernize archetype DERIVES from it; build / migrate / review / specify / explore consume the SAME domain model — none OWN it. Use when: "extract the business rules / domain model from this codebase", "build a requirements graph from the code", "what does this system actually require", "reverse-engineer the domain before we build/port/migrate". Works on ANY codebase (modern or legacy) — the value is the domain model, not the porting. NOT the code transform itself (that is the archetype consuming this model). This skill produces the DOMAIN MODEL, not new code.
biff
stephenh
Open Biff's local diff-review UI and address the user's inline review comments and replies. Use when the user invokes /biff or asks to review your changes in Biff.
docs_code
vuralserhat86
Code comments, JSDoc/TSDoc ve changelog best practices.
implementation-guide
nbbaier
Generate comprehensive implementation guides for coding tasks instead of writing code directly. Use when the user requests detailed implementation documentation, step-by-step development guides, or when they want to implement features themselves using tools like Cursor. Creates exhaustive guides with background context, architecture decisions, milestones with verification points, and rationale for a "build-it-yourself" workflow.
clinvar-database
ovachiever
"Query NCBI ClinVar for variant clinical significance. Search by gene/position, interpret pathogenicity classifications, access via E-utilities API or FTP, annotate VCFs, for genomic medicine."
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."
code-review-practices
armanzeroeight
Provides practical guidance for conducting thorough code reviews that identify issues early, promote knowledge sharing, and deliver constructive feedback. This skill should be used when reviewing pull requests, establishing team review standards, or mentoring developers on effective review practices.
api-docs-generator
armanzeroeight
Generates API documentation from code including OpenAPI specs, JSDoc, and Python docstrings. Use when documenting APIs, REST endpoints, or library functions.