Comments
Code comments and annotations
ado-deliver
by GitQuuu
Builds one approved Azure DevOps Task end to end with the agent team - picks the next Task tagged agent-ready (or a given id), claims it, creates a branch, runs fullstack-developer, tester and reviewer, then commits, pushes, opens a linked pull request and updates the work item. Use when the user says take the next task, deliver task 456, work the backlog, or similar.
github-issue-to-pr
by HMS091
"Carry a GitHub issue to a verified PR with honest CI state."
findmy
by HMS091
"Track Apple devices/AirTags via FindMy.app on macOS."
ado-backlog
by GitQuuu
Conventions for running the QuGents agent team from an Azure DevOps (Scrum) backlog - work item types and fields, the agent tag workflow (agent-plan, agent-proposed, agent-ready, agent-working, agent-pr-open, needs-human), WIQL queries, branch/commit/PR naming and the Azure DevOps MCP tools. Loaded by ado-plan and ado-deliver; use directly when reading or updating backlog items for the agents.
github-issues
by HMS091
"Create, triage, label, assign GitHub issues via gh or REST."
ado-plan
by GitQuuu
Plans Azure DevOps Product Backlog Items for the agent team - reads PBIs tagged agent-plan (or a given PBI id), has the planner agent break each into tasks, and creates them as child Tasks tagged agent-proposed for the product owner to approve. Use when the user says plan the backlog, plan PBI 123, break down this item, or similar.
gitmoot
by gitmoot
Use Gitmoot for local-first AI agent coordination across repositories, goals, reviews, GitHub PR comments, agent subscriptions, daemon checks, stuck jobs, branch locks, agent-templates, template capture and publish/pull, custom prompt agents, orchestration, heartbeats, pipelines, pipeline chaining through the localhost bridge, routing telemetry, event webhooks, the web dashboard, per-job runtime overrides, the config-driven runtime metadata registry, and Codex, Claude Code, Kimi Code, or omp runtime workflows.
beacon-triage
by Up-Coast
Triage Beacon feedback reports on a GitHub repository — the bug, feature and feedback issues filed from inside an app by the Beacon SDK. Use when asked to "triage the reports", "go through the beacon issues", "work the bug queue", "triage feedback", or when a scheduled run fires. Reads every open issue labelled beacon that isn't yet triaged, checks each one is complete, checks it against what the product is actually supposed to do, reproduces it, fixes and merges only the ones that meet the simple bar, and leaves everything else labelled and explained.
Excalidraw Generation
by rhuss
This skill should be used when the user asks to "create excalidraw diagram", "generate excalidraw", "hand-drawn diagram", "sketch diagram", "whiteboard style diagram", or when informal, spatial, annotated diagrams would best convey conceptual relationships. Expert in both presentation design AND artistic Excalidraw JSON creation.
biff
by 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.
debate-shuff
by patrickshuff
Challenge a position and engage in constructive debate as Patrick Shuff would, with intellectual honesty and substantive reasoning
capitaliser
by encrine-ai
Après une modification de la classe, verser ce qu'elle a appris là où la prochaine session le trouvera — le bon skill, un script de contrôle, AGENTS.md, le message de commit — et, si la leçon vaut pour toutes les classes, la remonter au moteur (skill remonter-au-moteur) — au lieu de la laisser dans la conversation. À utiliser en fin de tâche dès qu'une correction de l'enseignant, une erreur, un piège d'une source d'images, un défaut d'impression ou une décision de pédagogie est apparu ; et quand la demande dit « retiens ça », « note-le pour la prochaine fois », « il ne faut plus que ça arrive », « mets à jour les skills », « qu'est-ce qu'on a appris ? ».
trier-remontees
by encrine-ai
RÉSERVÉ AU DÉPÔT DU MOTEUR (encrine-ai/moteur), jamais dans une classe — l'entretien de la boîte du moteur, lancé chaque nuit par la tâche planifiée « l'agent moteur (remontées) » ou à la demande du propriétaire. Il fusionne le lot de remontées que le propriétaire a validé (son OK, et le sien seul), le propage aux classes du propriétaire par synchroniser-moteur avec tous les contrôles jusqu'au PDF, vérifie en ligne et ferme les issues ; puis il qualifie les nouvelles issues arrivées par remonter-au-moteur (acceptée, déjà faite, doublon, hors moteur, refusée), et intègre les acceptées dans UNE seule demande de fusion groupée (branche remontees/lot), contrôles verts, qui attend l'OK. Se déclenche sur : « trie les remontées », « traite les issues du moteur », « passe la boîte du moteur », « qu'est-ce que les classes ont remonté ? », « intègre le lot de remontées », « propage le lot fusionné aux classes », « mets toutes les classes à jour avec le nouveau moteur », « OK » en réponse au message « Moteur Encrine », « /trier-remontees ». Dans une classe, signaler un problème relève de remonter-au-moteur, et mettre sa classe à jour de synchroniser-moteur.
forgejo-issues
by jumbleknot
The MCM backlog lives in this repository's Forgejo issue tracker. Use when filing, finding, updating or closing backlog items, or when deciding whether work belongs in the backlog rather than in the current change.
create-controller
by jim60105
Create an API controller for a given entity in an ASP.NET Core Web API project. Use when the user wants to scaffold a new controller, create REST API endpoints, or set up CRUD operations with Entity Framework Core and OpenAPI annotations.
seuratmap2ref
by pwwang
Map query single-cell datasets to high-quality reference atlases using Seurat's reference mapping workflow. Performs label transfer, UMAP projection, and integration with reference annotations without modifying query expression data. Enables transfer learning from curated atlases like Azimuth PBMC or custom tissue-specific references.
github
by i9wa4
GitHub operations guide using gh CLI. Use when: - Working with GitHub Issues - Managing sub-issues (parent-child relationships) - Posting comments to a PR - Posting inline comments to a PR - Replying to PR comments - Checking diffs with line numbers
docs
by lukeslp
"Documentation generation and technical writing skill. Use when: creating README files, writing API documentation, generating code documentation (Python docstrings, JSDoc), building user guides, producing architecture overviews, or improving existing documentation quality."
pr-reviewer
by synaptent
Multi-agent adversarial code review for pull requests
documentation-and-adrs
by ToanMobile
Dùng khi quyết định kiến trúc, chọn dependency/pattern/data model, đổi public API hoặc cần lưu why/trade-off lâu dài. Bỏ qua thay đổi tầm thường và fact đã suy ra được từ code/git.
super-collect
by ToanMobile
Find problems in one project and file them as tickets into its super-board Backlog — the board fixes them. Source plug-ins - sentry (app errors), posthog (exceptions, rage/dead clicks, failure events, web vitals, tracking gaps), github (issues not on the board), prs (recurring problems in merged PRs and their review comments), architecture (refactor findings), plus any custom source added in onboard (an MCP server, HTTP API, CLI command or app). Each candidate is checked by one fresh verifier before filing. Dry-run by default. Use when the user says "super-collect", "/super-collect", "/super-collect sentry", "collect tickets", "triage errors onto the board", "what keeps breaking", or "find refactors".
super-review
by ToanMobile
Reviewer lane of the super-board pipeline and standalone PR/branch readiness review — forms its own hypotheses before reading the builder's summary, remembers prior findings and re-checks each with file:line proof, runs an adversarial truth-check on non-trivial diffs, and classes every finding (Gap, Bug, Verification miss, Scope drift, Over-engineering via ponytail:ponytail-review). Merges only through super-board-merge-gate.sh, pinned to the reviewed head SHA, and routes other fixes to Super Build or Super QA via the board. Use when the user says "Super Review", "review this branch", "review loop", "make sure this is merge-ready", "PR review", or asks for code, architecture, security, QA evidence, or release-readiness judgment.
super-qa
by ToanMobile
Super QA canonical workflow for functional bug-bash, evidence capture, and fix-ready issue filing. Crawls routes from docs/super-qa/queue.md with Playwright, records screenshots/logs/HARs, files product-readable issues with clear type/priority/area labels, and continues until traversal is complete or only human-gated blockers remain. Crawling is always browser-driven, but the regression test it leaves behind is written at whichever layer the defect actually lives — unit or integration in Vitest, e2e in Playwright only when the browser is the thing that broke. Use when the user says "run super-qa", "QA review", "bug bash", "verify and fix", or invokes /super-qa.
super-build
by ToanMobile
Builder lane of the super-board pipeline — takes a Ready GitHub Project card into its own per-issue git worktree, makes the smallest safe change test-first (TDD, ponytail simplest-first, official docs first for third-party APIs, upgrades and auth/billing), opens a draft PR and hands it to QA and Review through the board; it never merges — merges go through the Reviewer's merge gate. Inside super-board run it runs as a lane agent in the in-session wave workflow (workflows/super-board-wave.js, no worker cap unless max_workers is set); standalone headless claude -p dispatch is legacy opt-in. Use when the user says "Super Build", "run the build loop", "/super-build", or invokes the skill.