23 skills (repositories by bioinformatist) · sorted by popularity
Plan or implement retirement of a system, API, feature, persisted configuration, or database shape. Use for compatibility cutovers, explicit deprecation review, or an explicit unreleased replacement decision, including determining whether consumers or data exist; not ordinary dependency bumps, local renames, prose edits, or generic architecture discussion.
The English summary is being prepared. Showing the original description.
Design, review, or report a measured performance comparison. Use for benchmark methodology, speedup or regression claims, and performance-based choices; not generic performance discussion, ordinary dependency bumps, local renames, or prose edits.
The English summary is being prepared. Showing the original description.
Trace what an actual code change could break beyond its diff when interfaces, serialized data, database schemas, configuration, caches, lifecycle ordering, or cross-language consumers are involved. Use for explicit impact analysis; not local renames, prose edits, ordinary dependency bumps, or generic architecture discussion.
The English summary is being prepared. Showing the original description.
Explicit retrospective of a coding session with evidence-backed suggestions for future work.
The English summary is being prepared. Showing the original description.
Explicitly build a disposable logic or UI prototype to answer one design question.
The English summary is being prepared. Showing the original description.
Disciplined diagnosis loop for hard bugs, regressions, flaky failures, and performance problems with unclear cause. Use for root-cause debugging after a concrete symptom exists; do not use for routine implementation or speculative cleanup.
The English summary is being prepared. Showing the original description.
Explicit-only interview loop for stress-testing a plan, decision, or idea. Use only when the user asks to grill, interrogate, interview, or stress-test their thinking before action.
The English summary is being prepared. Showing the original description.
Explicit-only workflow that writes a redacted continuation handoff to a unique temporary Markdown file. Use only when the user explicitly asks for a handoff for another session.
The English summary is being prepared. Showing the original description.
Automate browser interactions, inspect web pages, and work with Playwright tests using a headless-first CLI workflow.
The English summary is being prepared. Showing the original description.
List every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.
The English summary is being prepared. Showing the original description.
Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for "review this", "code review", "review the last commit", "review my PR", "is this over-engineered", /ponytail-review.
The English summary is being prepared. Showing the original description.
Prose final-pass editor for GitHub issue bodies, pull request bodies, release notes, README/docs changes, public comments, and user-facing explanations. Use when Codex drafts or revises substantial prose that will be published or committed, especially when the user asks to polish, de-slop, make it less AI-written, improve a PR/issue body, or prepare docs text; do not use for ordinary code implementation, debugging transcripts, logs, quoted text, command output, API names, or Chinese conversational replies unless explicitly requested.
The English summary is being prepared. Showing the original description.
Explicit-only request to restate the previous explanation plainly in the current conversation language while preserving facts and uncertainty.
The English summary is being prepared. Showing the original description.
Use native Worktrunk commands for explicit Git worktree operations when requested. Distinguish repository selection from worktree selection, and inspect command help before changing configuration or hooks.
The English summary is being prepared. Showing the original description.
Audit a codebase as a read-only senior advisor, prioritize evidence-backed improvements, and write self-contained implementation plans. Use for codebase audits, improvement roadmaps, focused planning, plan review, plan reconciliation, or executing an existing improve plan through an isolated Codex worktree. The advisor never edits source code; execution uses codex-improve and returns to the main agent for review.
The English summary is being prepared. Showing the original description.
Quality audit of a whole repo: bugs, security holes, what breaks under real load, risky code without tests, slow paths, and what to delete, merge or split. Ranked, each finding explained in plain English. One-shot report, changes nothing. Use for "audit this codebase", "review the whole repo", "find bloat", "what can I delete", /ponytail-audit.
The English summary is being prepared. Showing the original description.
Test-driven development with red-green-refactor and behavior-focused tests. Use when the user explicitly wants test-first work, a regression test before a fix, or integration tests that drive a feature through a public interface.
The English summary is being prepared. Showing the original description.
Explicit-only workflow that writes a safe Markdown questionnaire for another person. Use only when the user explicitly asks for a questionnaire.
The English summary is being prepared. Showing the original description.
Write substantial agent-consumed guidance such as skills, AGENTS.md instructions, and documents reached by agent context pointers. Do not use for ordinary README or user-facing prose.
The English summary is being prepared. Showing the original description.
Build and sharpen a project's domain model. Use only when actively changing glossary or ubiquitous-language terms, or recording a durable architectural decision; merely reading a glossary is not a trigger.
The English summary is being prepared. Showing the original description.
Route requests for current library, framework, SDK, API, CLI, or cloud-service documentation through available documentation tools and primary sources.
The English summary is being prepared. Showing the original description.
Read public X/Twitter post URLs as structured evidence through the ADHX API. Use for relevant user-provided or research-discovered x.com, twitter.com, or adhx.com links. ADHX does not search X, and long-form Article content may be incomplete.
The English summary is being prepared. Showing the original description.
Shared vocabulary for designing deep modules, interfaces, seams, adapters, leverage, and locality. Use when designing or reshaping module boundaries, making code more testable, or evaluating interface depth.
The English summary is being prepared. Showing the original description.