Comments
Code comments and annotations
untaped-jira
by alexisbeaulieu97
Use the untaped jira command to work with Jira Data Center or Server issues (search with JQL, read, create, edit, assign, comment on, link and transition issues, and list projects, boards and sprints). Use when the user mentions Jira, a ticket or issue key such as OPS-123, JQL, a sprint or board, or moving an issue to another status.
findmy
by magnetoid
"Track Apple devices/AirTags via FindMy.app on macOS."
loop
by sequant-io
"Quality loop - Parse test/QA findings and iterate until quality gates pass"
codex-spec-review
by varigg
Iterative Codex CLI review of a spec issue on the project tracker
maintain-docs
by timmo001
Keep documentation current and accurate with recent code changes, across in-code docs (docstrings, annotations, comments), in-repo docs sites, and external docs repositories. Use when asked to update docs, check docs accuracy, keep documentation current, document recent changes, refresh docstrings or annotations, or catch documentation up with the codebase. Matches the codebase's existing documentation density and stops before commit.
art-of-comment
by rakaadi
This is your guide for giving a comments within the codebase, whether it's a inline comment or a comprehensive JSDoc style comment. Use this skill when you generate a code for bugs fixing, building a new components, refactoring and implementing new features.
SakJules-SakSee-github-issues
by beer-sakthai
"Create, triage, label, assign GitHub issues via gh or REST."
documentation-writer
by jgarrison929
Use when writing API documentation, READMEs, changelogs, architecture decision records (ADRs), migration guides, onboarding guides, troubleshooting docs, code comments, or any technical documentation task.
adr
by srobroek
Register an architecture decision as a beads decision bead. Use when a hard-to-reverse choice is made, when superseding one, or when bd lint reports findings.
home-assistant-lazy-context
by timmo001
'Home Assistant frontend lazy-context, memoization, and hass removal guidance. Use when migrating Lit components from hass!: HomeAssistant, .hass=${...}, or broad hass access to context slices.'
how
by scottwater
Explain how a subsystem works or where code should live. Use for runtime walkthroughs, architectural ownership, layering questions, and architecture critique; use why for historical motivation.
assess
by sequant-io
"Issue triage and status assessment - analyze current state, detect health signals, and recommend next action with full workflow plan."
docs
by coreindustries
"Generate and update project documentation."
explain
by laststance
Deep, systematic explanation of code, concepts, and system behavior. Always operates at advanced level with introspection markers and validation. Analyzes target thoroughly before explaining, verifies accuracy after. Use when: - User asks "what does this do", "how does this work", "explain this" - User wants to understand code, architecture, or a concept in depth - User points to a file, function, or system and asks for explanation - User says "explain", "walk me through", "teach me", "break down" Keywords: explain, understand, how, what, why, walk through, teach, break down, clarify
Tech Tutor (Ren Nakamura Persona)
by PrakharMNNIT
Intuition-first tech mentor who makes complex concepts click through visuals, analogies, and the 6-layer explanation framework. Use this skill when the user asks to "explain", "tutor", "teach", "mock interview", or needs intuition regarding DSA, System Design, or AI/ML.
reviewer-response
by BasileChretien
Answer a journal's reviewers point by point, with every claimed revision checked against the manuscript as it was sent. Use when a decision letter with reviewer comments arrives, before revising anything, when check reports point-unanswered, response-claims-nothing, claimed-change-did-not-happen, claimed-change-missed-the-point or anchor-unrecorded, or before resubmitting.
paper-audit
by BasileChretien
Check the numbers in a paper that was not written with manuscript-guard against the analysis outputs, and report honestly what a match is worth. Use when handed an existing .docx or Markdown manuscript whose numbers were typed by hand, before resubmitting an old paper, or before moving one into a manuscript-guard project.
docstring-and-jsdoc
by CMSForNerd
"Enforces PEP-257 Google-style docstrings for Python and detailed JSDoc comments for JavaScript/Node.js utilities."
word-roundtrip
by BasileChretien
Send a co-author a Word document built from the Markdown source, and bring their edits and comments back without letting a hand-typed number or citation in. Use when a co-author wants a .docx to edit, when an edited .docx comes back, or before running manuscript-guard import.
query-optimizer
by CuriousLearner
Analyze and optimize SQL queries for better performance and efficiency.
issue-start
by shoji9x9
GitHub Issue を起点に作業開始フローを標準化するスキル。Issue URL や Issue 番号を受け取り、リポジトリ一致確認・feature ブランチ作成と checkout（gh issue develop）・調査・実装・commit・push・PR 作成までを段階的に進めたいときに使う。ブランチを用意した時点で呼び出し元へ返す --branch-only があり、実装を自分で持つスキルからの委譲に使う。push の前と --acceptance で、Issue の受け入れ条件を 1 項目ずつ根拠と突き合わせた表を同梱の検査で確かめる。「Issue から始める」「この issue に着手」「受け入れ条件を確かめて」「issue-start」や、--branch-only / --plan / --commit / --pr / --acceptance を伴う依頼で発動する。
pr-comment-analysis
by auldsyababua
Extract, consolidate, and prioritize all comments from GitHub Pull Requests for systematic code review. Fetches both inline review comments and general PR conversation, then analyzes and organizes them by priority (critical bugs/security, design improvements, style nitpicks). Use when working with PR reviews, consolidating feedback from multiple reviewers, or creating action plans from review comments.
mail-contacts
by aashari
Extract contacts and build a communication directory from email history. Find email addresses, frequency of contact, and relationship strength. Use when user wants to find someone's email address, see all contacts, or understand their communication network. Arguments: optional person name, company, domain, or "top contacts" / "recent contacts".
codebase-documenter
by auldsyababua
This skill should be used when writing documentation for codebases, including README files, architecture documentation, code comments, and API documentation. Use this skill when users request help documenting their code, creating getting-started guides, explaining project structure, or making codebases more accessible to new developers. The skill provides templates, best practices, and structured approaches for creating clear, beginner-friendly documentation.