Comments
Code comments and annotations
gcse-biology-tutor
by markpitt
GCSE Biology tutor and revision assistant for 15–16 year old students preparing for 2026 exams across AQA, Edexcel, OCR, and WJEC boards. Use when a student asks for help understanding biology topics, answering exam questions, revising for GCSEs, practising required practicals, or wants guidance on exam technique for GCSE Biology.
gcse-history-tutor
by markpitt
GCSE History tutor and revision assistant for 15–16 year old students preparing for 2026 exams across AQA, Edexcel, OCR, and Eduqas/WJEC boards. Use when a student asks for help understanding history topics, answering exam questions, revising for GCSEs, practising source analysis, writing essays, or wants guidance on exam technique for GCSE History.
evaluate-enrichment
by monarch-initiative
Use when evaluating a GO enrichment method or a GOA evidence variant (all vs IBA vs IBA+IEA vs no-contributes_to) against the curated benchmark in this repo — the IBA/evidence-ablation eval. Covers building queries.gmt, prepare_go_eval, running genesets-rs, and scoring with the confirmatory/mechanistic split and the recovery_status diagnostics, plus the don't-refit-the-gold guardrail.
curate-geneset
by monarch-initiative
Use when curating or reviewing a GO-term interpretation of a non-GO gene set (MSigDB C8/C2/H, literature disease-activity, or GWAS/CRISPR genetics) for the curation/ gold standard in this repo. Covers grounding in the real membership, OLS term verification, the category / recovery_status / insight axes, evidence, series, the 4-gate validator, and folding the set into the eval.
clean-code-skill
by darellchua2
Write clean, human-readable code with proper naming, small functions, self-documenting patterns, and object calisthenics - language-agnostic
docx-creation-skill
by darellchua2
Create, read, edit Word (.docx) — TOCs, headings, letterheads, tracked changes, comments, images; report/memo/letter/template deliverables. Not PDFs, spreadsheets, or Google Docs.
receiving-code-review
by yishan-io
Use when receiving code review feedback, before implementing suggestions, especially when feedback is unclear, broad, or may not fit the codebase as-is.
how-to-use-tortoise
by daniel-ospina
Create points, operators, mitigations, NANDs, supersede, delete, and annotate on the Tortoise graph. Use when asked to write to the Tortoise graph — creating points, operators, mitigations, NAND edges, superseding points, deleting, or annotating.
dev-uat-promotion-skill
by darellchua2
Orchestrate batch dev-to-uat branch promotion across many repos — remote dedup, fast-forward vs back-merge vs uat-only classification, protected branch PR fallback, verification, and per-ticket result comments.
workspace-observer-onboarding
by sindre-ai
Guides the Workspace Coach to run onboarding for a new workspace — detecting an empty workspace, creating an onboarding session, identifying the owner, and posting context prompts in sequence to get the workspace to its first bet.
/check-pr
by blamechris
"Address all PR review comments systematically and respond inline."
/batch-merge
by blamechris
"Sequentially merge a set of reviewed PRs, handling branch protection's \"must be up-to-date\" requirement by updating each branch after the previous merge."
/decompose-issue
by blamechris
"Break a single GitHub issue that is too large into 2-5 independently implementable sub-issues."
/tackle-issues
by blamechris
"Run an unattended marathon session that works through GitHub issues across multiple waves until convergence — all issues are resolved, or all remaining..."
OpenVibely GitHub Autonomous SDLC Bootstrap
by openvibely
Software factory for running coding agents at scale across projects.
clean-code
by uwuclxdy
Clean code principles and best practices covering naming conventions, function design, error handling, comments, and architecture. Use this skill whenever the user asks you to write, review, or refactor code and wants it to follow clean code standards. Also trigger when the user mentions "clean code", "code quality", "readability", "refactor for clarity", "naming conventions", "function size", "code smells", or asks for a code review with best practices in mind. Apply these principles proactively when writing or reviewing code, even if the user doesn't explicitly ask for "clean code."
/agent-review
by blamechris
"Launch an expert code reviewer agent with full project context."
/create-issue
by blamechris
"Create a standardized GitHub issue with labels and traceability."
civiltekk-ponytail-audit-skill
by darellchua2
Over-engineering audits and debt tracking — whole-repo audit (ranked delete/stdlib/native/yagni/shrink findings, net removable count, one-shot report), diff-only review (concrete replacements), and ponytail: comment harvest into a debt ledger (ceiling + upgrade trigger per marker, no-trigger rot). Triggers: audit for over-engineering, find bloat, what can I delete, over-engineered diff, simplify this change, review for bloat, ponytail shortcuts, what did ponytail defer, tech debt markers.
/full-review
by blamechris
"Run a complete review pipeline: agent-review first, then check-pr."
/autonomous-dev-flow
by blamechris
"Orchestrate long-running autonomous dev sessions — work through GitHub issues sequentially with TDD, create PRs, run /full-review, then merge or flag..."
/parallel-dev
by blamechris
"Orchestrate parallel autonomous dev sessions — dispatch multiple agents into isolated worktrees to implement GitHub issues with TDD simultaneously, then run..."
quiz
by TakaGoto
"Test your understanding of a RAG concept"
journal
by TakaGoto
"Write a quick note about what you learned or what confused you"