Comentaris
Comentaris i anotacions del codi
codex-explain
sd0xdev
"Explain complex code via Codex MCP. Use when: understanding complex logic, tracing data flow, onboarding to unfamiliar code. Not for: code review (use codex-code-review), exploration (use code-explore). Output: structured explanation at chosen depth."
jj-history-investigation
edmundmiller
Investigate jj commit history, split commits, annotate file changes, and clean up redundant commits. Use when debugging history, splitting large commits, or explicitly authorized history rewrites.
pr-review
edmundmiller
Review GitHub pull requests with structured analysis and gh CLI integration. Use when asked to "review a PR", "check my PRs", "review pull request", or help with code review workflows.
springboot-migration
a-pavithraa
Migrate Spring Boot projects to version 4.0 with Java 25, including Spring Modulith 2.0 and Testcontainers 2.x upgrades. Use when user requests upgrading Spring Boot, migrating to Java 25, updating dependencies to Spring Boot 4, mentions Jackson 3 migration, asks about starter renames (web→webmvc, aop→aspectj), fixing test annotations (@MockBean→@MockitoBean), or needs help with Spring Modulith 2.0 or Testcontainers 2.x compatibility. Analyzes codebase for migration issues and guides through changes with specific file references.
tufte-test
edmundmiller
Review charts with a simple Tufte-style rubric. Use when judging whether a chart is clean, honest, readable, and insight-forward, or when iterating on a visualization until it passes a concise quality bar.
mentor
mcouthon
"Guide through problems with questions, not answers using Socratic teaching style. Use when asked to teach, explain concepts through discovery, help learn, or guide understanding without giving direct solutions. Triggers on: 'use mentor mode', 'teach me', 'help me understand', 'guide me', 'mentor', 'I want to learn', 'explain by asking', 'Socratic', 'don't give me the answer'. Read-only mode - explores and guides but doesn't write code."
agentskill
airscripts
Analyze a code repository and synthesize an AGENTS.md.
sc-explain
htlin222
Provide clear explanations of code, concepts, or system behavior. Use when user asks to explain code, understand behavior, or learn concepts.
github
atrislabs
GitHub integration via AtrisOS API. Manage PRs, issues, branches, CI status, code review, search. Use when user asks about repos, pull requests, issues, branches, or code changes.
git-history-recon
Jamie-BitFlight
Analyze git repository history to produce a codebase risk profile before code review. Probes repo size, runs 7 parallel git analysis pipelines (hotspots, bug magnets, bus factor, contributor momentum, firefighting frequency, newly added files), cross-references hotspots with bug magnets to identify high-risk files with primary owner annotation, and writes walkthrough/recon-report.md. Use before code review to prioritize reviewer attention, at the start of linear-walkthrough Phase 1 Discovery to weight file coverage, or when onboarding to an unfamiliar codebase.
code-review-python
Jamie-BitFlight
Provides Python-specific code review rules for the dh code-reviewer agent. Activates on pyproject.toml or *.py file detection — enforces uv, ruff, ty, pytest, type annotation, error handling, and Python 3.11+ idioms including pathlib, match statements, and modern union syntax.
backlog
Jamie-BitFlight
Use when structured backlog operations are needed through MCP or the provider-neutral CLI. For Beads-native issue and dependency work, use bd directly.
cove-prompt-design
Jamie-BitFlight
Explains Chain of Verification (CoVe) prompt design — a 4-step pattern separating generation from independent factual verification. Use when designing prompts that require factual accuracy, reducing hallucinations, checking technical standards or APIs, or producing step-by-step procedures where subtle errors are costly.
go-google-style-guide
metalagman
Expertise in Go programming according to the Google Go Style Guide. Use when the user needs to write, refactor, or review Go code for clarity, simplicity, and maintainability. This skill ensures adherence to Google's official Go idioms, formatting, and the "Least Mechanism" principle.
easy-query-expert
cc123hh
Guidance for Easy-Query ORM (Java), covering type-safe proxy queries, implicit joins, and tracking updates.
social-autoposter
m13v
"Automate social media posting across Reddit, X/Twitter, LinkedIn, and Moltbook. Find threads, post comments, create original posts, track engagement stats. Use when: 'post to social', 'social autoposter', 'find threads to comment on', 'create a post', 'audit social posts', 'update post stats'."
social-autoposter
m13v
"Automate social media posting across Reddit, X/Twitter, LinkedIn, and Moltbook. Find threads, post comments, create original posts, track engagement stats. Use when: 'post to social', 'social autoposter', 'find threads to comment on', 'create a post', 'audit social posts', 'update post stats'."
process-reviews
flonat
"Process referee comments from a reviews PDF into standardised tracking files: comment tracker, review analysis, and LaTeX verbatim transcription. Triggers: 'got referee comments', 'process reviewer feedback', 'R&R response'. Not for writing the response — this extracts and organises the comments."
add-educational-comments
LeoYeAI
'Add educational comments to the file specified, or prompt asking for file to comment if one is not provided.'
review-briefing
leodearden
"Create and maintain the review briefing — a project-specific context file that tells the /review skill what matters about a project: purpose, important scenarios, architectural decisions, conventions, and known gaps. The briefing captures durable truths that can't be inferred from code alone — not code structure (which goes stale). ALWAYS use this skill for: /review-briefing commands, creating or updating review/briefing.yaml, setting up review context for a project, when the user says 'create a review briefing' or 'update the briefing', and when /review suggests running /review-briefing because no briefing exists. Also use when the user wants to validate their existing briefing or see what's changed. This is NOT for: running the actual review (/review), implementing code, or fixing issues found during review."
recon-escalation-watcher
leodearden
"Watch and close fused-memory's RECONCILIATION escalation queue (port 8103) in a long-running loop. This is the consumer for the recon queue — the integrity/operational findings the reconciliation harness files, NOT the orchestrator's task-pipeline escalations (those are escalation-watcher's job, ports 8100/8102). Use when the user says 'watch recon escalations', 'monitor the fused-memory escalation queue', 'babysit reconciliation', mentions the 8103 queue, recon_integrity_issue / recon_failure / recon_stale_run findings piling up, or wants the reconciliation queue triaged and closed. This is a continuous loop skill; the watcher is the SOLE closer of the recon queue (recon never resolves its own findings). This is NOT for orchestrator task escalations, blocked tasks, merge failures, or worktrees."
escalation-watcher-auto
leodearden
"Autonomous level-1 escalation watcher. Acts as the L1 consumer and triage funnel to the human (L2): handles admin-class escalations directly (scope_violation, dependency_discovered, cleanup_needed), performs shallow root-cause analysis to detect causal clusters, and promotes judgement-class items — single or clustered — to L2 via promote_to_l2 so the human receives a pre-formed hypothesis with evidence and concrete options. When promote_to_l2 is unavailable (graceful degradation), falls back to the legacy leave-pending + digest mode. Runs until ROTATION_ESCALATIONS or ROTATION_HOURS is reached, then exits cleanly. This is a fully autonomous, no-terminal skill — do NOT use it for interactive unblocking."
curate-fused-memories
leodearden
"Run the memory-consolidation curation sitting: batch-rule the backlog of 'Human gate: consolidate duplicate cluster' tasks and execute the resulting consolidations against the fused-memory Mem0 corpus under the gate-3200 retain-and-tag shape. Use when the user says 'run the curation sitting', 'consolidate duplicate memories', 'batch-rule the consolidation gates', 'clean up the Mem0 corpus', 'curate memories', 'adjudicate the duplicate-cluster gates', or wants the memory-consolidation backlog (task 3524 / esc-3524-1) worked. This is NOT for: ordinary memory writes (use /memory), the reconciliation escalation queues (recon-escalation-watcher), unblocking stuck tasks (/unblock), or a single ad-hoc near-exact dedup that recon Stage 1/2 can absorb inline — per the 2026-08-02 policy, new clusters route through inline Stage 1/2 consolidation, not new gate tasks."
escalation-watcher
leodearden
"Watch for and handle level-2 escalations from the dark-factory orchestrator in a long-running loop. Under the 3-tier escalation ladder (L0→per-task steward, L1→escalation-watcher-auto, L2→human), this skill is the L2 consumer. Use this skill when the user wants to monitor escalations, says 'watch escalations', 'handle escalations', 'babysit the orchestrator', or wants a long-running session to catch and triage issues that the auto-watcher couldn't resolve. Also trigger when the user starts an orchestrator run and asks you to keep an eye on it, mentions escalations piling up, or wants automated escalation handling. This is a continuous loop skill that runs until stopped."