By sejas
Spec-driven development skills that leverage AI to optimize daily coding workflows and improve productivity.
Use when the user wants to name or rename something — a product, feature, brand, project, command, or company — or asks to "brainstorm names", "find a better name", "naming ideas", or invokes /brainstorming-names.
Write a commit message and create a git commit. Use when the user wants to commit changes, asks for a commit message, or says "commit this" or "make a commit".
This skill should be used when the user asks to "set up a status line", "configure the footer", "show context window usage", "add a statusline", "visualize context window", "customize the Claude Code footer", or wants to display token counts, cost, or session metrics in the Claude Code terminal footer.
Use when the user asks to create AGENTS.md, generate agent instructions for a repository, set up CLAUDE.md, or wants to document project conventions for coding agents. Also use when user says "create agents md", "setup agent docs", or "initialize repo for agents".
Search the codebase for function source code and explain it like for a junior developer
Based on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A flat collection of Claude Code skills and supporting hooks for development, presentations, and content workflows.
These are the skills I (Antonio Sejas) use day-to-day across Automattic work and personal projects. They are intentionally small, single-purpose, and composable — drop in whichever ones you find useful.
skills/ # one folder per skill, each containing SKILL.md
hooks/ # standalone hook scripts grouped by purpose
No plugin manifest, no marketplace — just drop the folders where you want them.
Copy or symlink any skill into ~/.claude/skills/:
ln -s "$PWD/skills/commit" ~/.claude/skills/commit
Or symlink the whole directory to expose every skill:
for d in skills/*/; do ln -s "$PWD/$d" "$HOME/.claude/skills/$(basename $d)"; done
Each skill is invoked by typing /<skill-name> in Claude Code, or by triggering a phrase from the skill's description (Claude auto-routes).
| Skill | What it does | How I use it |
|---|---|---|
commit | Drafts a Conventional Commit message from the staged diff and creates the commit. | /commit when staging is ready. Lets me skip writing commit subjects by hand. |
explain | Locates a function in the codebase and explains it for a junior dev. | /explain handleAuth when onboarding to a new repo. |
worktree | Creates an isolated git worktree from origin/trunk in ~/worktrees.nosync/, copies node_modules. | /worktree feat/new-thing to start parallel feature work without polluting the main checkout. |
pr-review | Lists PRs awaiting my review, checks out each branch, runs the linter, and writes a structured review doc. | Daily review pass — pick one off the list and let the skill set up the workspace. |
quick-pr-review | Lightweight diff review against a GitHub PR URL (no checkout). | When I just need a fast read on a colleague's PR. |
ai-prs | Lists open PRs targeting the Studio AI command with status/approval/reviewers. | Triage Studio AI PRs before standup. |
react-doctor | Scans recent React changes for common issues (hook deps, key warnings, state misuse). | After finishing a React feature, before /commit. |
create-agents-md | Generates AGENTS.md / CLAUDE.md for a repository documenting conventions and structure. | When starting a new repo or onboarding a coding agent. |
studio-debug | Inspects WordPress Studio local sites — SQLite DB, logs, plugin/theme issues. | When a Studio site misbehaves locally. |
teach | Acts as a teacher that makes me deeply understand the current session — problem, solution, edge cases, broader impact — via a running checklist, incremental confirmation, and quizzes (AskUserQuestion). | /teach after Claude lands a non-trivial change I want to actually internalize, not just merge. |
score | Calibrated 0–10 judging of any artifact — website/UI (screenshot), markdown draft (direct read), or code diff. A fresh judge subagent reasons first (strengths/weaknesses/improvements/reasoning), score last, with calibration anchors and a pinned "what a 10 looks like" bar so improve-until-N loops converge instead of chasing moving goalposts. | /score the landing page, then a goal loop "repeat until 9/10" — the judge drives design/writing iteration. |
start-issue | From a Linear link or branch name: resolves the issue (Linear MCP, context-a8c fallback), spins up a worktree, implements the fix, verifies (lint/typecheck/tests, light+dark for UI), then commits, pushes, and opens a draft PR with the template filled in. | /start-issue <linear-link> to go from ticket to draft PR in one shot. |
unworktree | Reverse of worktree: absorbs a worktree's branch back into the main checkout — dirty-tree safety gate, removes the worktree, checks the branch out in the main repo. Set $MAIN_REPO to your main checkout. | When I'm done in a ~/worktrees.nosync/ branch and want to continue it in the main repo. |
explore-exploit | Generate-many-then-select for tasks with a large solution space and a measurable quality signal (naming, UI variants, copy, code/prompt tuning). Fans out candidates, scores them, and iterates toward the best — tournament / simulated-annealing style. | "Generate N options and rank them" or an iterate-until-score loop. |
npx claudepluginhub joshuarweaver/cascade-code-general-misc-3 --plugin sejas-ai-code-skillsWordPress development skills for Claude Code — local site management with Studio CLI, WordPress core contributions via Trac and Gutenberg, and Studio site debugging.
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
Matt Pocock's agent skills for real engineering — grilling, spec/ticket flows, TDD, code review, domain modelling and more. Plug-and-play, not vibe coding.
Access thousands of AI prompts and skills directly in your AI coding assistant. Search prompts, discover skills, save your own, and improve prompts with AI.
Evidence-gated AI coding workflow: scan → analyze → plan → TDD → execute → fix → verify → review, powered by Codebase Memory MCP >= 0.9.0 with optional Serena LSP intelligence. Includes blast-radius planning, test/cycle gates, independent review, and Windows Git Bash hook auto-resolution.
Persistent coding companion for Claude Code, Pi, and Oh My Pi. MCP-based terminal pet with ASCII art, stats, reactions, and personality.
Enterprise AI agent orchestration plugin with 150+ commands, 74+ specialized agents, SPARC methodology, swarm coordination, GitHub integration, and neural training capabilities