justinmchoi
UserReusable agent skills and baselines for Claude Code, Codex, and Copilot, with deterministic install/verify tooling
Categories
Indexed Skills (22)
baseline-gap-review
Reconcile the piled-up `_Improvements/` backlog against both toolkits' current baselines/skills, classify and place every note, and archive the source files with a disposition manifest. Use when the user asks to "review the improvements backlog", "reconcile _Improvements", do a "baseline gap review", or "check if anything needs promoting from _Improvements".
diagnose-migration-history-divergence
Diagnose EF Core migration-history divergence between a target environment's __EFMigrationsHistory table and a deploying or rolling-back branch's Migrations folder — trace each divergent migration to its origin branch/author/merge-status via git, classify its risk, and produce a hand-off report. Triggers on "migration history divergence", "migration was not found" deploy failures, "EF Core migration mismatch between environments", and "pending model changes" / rollback-planning questions before running Update-Database against a shared environment.
improvement-extraction
Scan the current session for candidate CLAUDE.md/AGENTS.md baselines or candidate Claude Code skills, and write them as structured notes to a configurable output folder for later manual review. Use when the user asks to extract improvement ideas, capture process improvements, or save candidate baselines/skills surfaced during this session — phrases like "extract improvements", "capture what we'd add to CLAUDE.md", or "save this as a candidate skill idea".
query-azure-devops
Query work items and pull requests from an Azure DevOps organization. Use when asked to pull tickets, stories, support requests, PRs, or activity summaries from Azure DevOps. Encodes the correct tech-path discovery sequence so you do not waste turns on dead ends.
session-closeout
Chain the personal end-of-session skills — a session-log capture skill, lesson-extraction, and improvement-extraction — into a single wrap-up pass instead of invoking them one at a time. Use when the user wants to close out, wrap up, or end a work/coding session and capture everything worth keeping in one go. Triggers on "wrap up this session", "close out", "let's wrap", "session closeout", "收工", "收官三連".
sql-backfill-pipeline-scaffold
Scaffold a multi-phase SQL Server backfill/data-recovery pipeline that walks a chain across multiple systems to recover a corrupted value — numbered phase scripts, a batched ID-input helper, a hard read-only-verify vs. mutate split that branches on row count, and a command-steps runbook.
setup-matt-pocock-skills
Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.
social-live-photo-card
Turn user-provided short videos, video collections, photo collections, or mixed media into a social-platform Live Photo card when one small motion point explains more than a static image, with collection screening, first-frame, duration, crop, and publish-path checks.
client-flow-diagrams
Create or revise high-level flow diagrams for client or non-technical audiences. Use when the user needs a workflow, process, integration, or system-interaction diagram that communicates business-level behavior without exposing implementation details.
diagnose
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
grill-with-docs
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
improve-codebase-architecture
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
methodology-intake
Evaluate an external article, repository, tool list, paper, framework, or workflow before promoting it into repo artifacts. Use when deciding whether outside methodology material should become a Rule, Skill, Context term, ADR, Spec, Issue, or No-op.
prototype
Build a throwaway prototype to flesh out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine, mock up a UI, explore design options, or says "prototype this", "let me play with it", "try a few designs".
setup-agent-team
Create a bounded manual execution packet for large AI-agent team workflows, or refuse/downgrade when the task should stay single-agent. Use when work is multi-domain, parallelizable, and context-heavy enough to need role selection, context packets, ownership boundaries, handoffs, budgets, verification, package-execution policy, and external-system credential policy before launching workers.
staff-level-review
Read-only engineering review with a fixed findings/verdict output contract. Use when the review needs that contract, a review context bundle, or a non-GitHub diff source (e.g. Azure DevOps, a patch file, a bounded set of repos and docs). For routine review of a local diff or GitHub PR, prefer the built-in /code-review or /review instead.
tdd
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
to-issues
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
to-prd
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
triage
Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
draft-handoff
Hand a drafted artifact to the user through the clipboard, with post-copy verification and on-demand re-copy, so the user can review it and paste it into a destination the agent must not or cannot write to directly (a review-gated personal vault such as Obsidian, a web form, another application). Trigger phrases include "copy for me", "幫我複製", "pbcopy", "過目再貼". Do NOT use when the agent can write the content into the target repo directly, or for multi-file transfers.
grill-spec
在還沒有具體計畫時盤問需求、術語、邊界與驗收條件，出口是第一個最小 vertical slice。Use when requirements are unclear and no concrete plan exists yet — the user has a goal or feature idea but scope, acceptance checks, or domain terms are still fuzzy. Do NOT use when a concrete plan already exists and needs challenging against documented decisions — use grill-with-docs for that.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.