Claude Skills by tomzx

Create a GitHub pull request with a structured description linked to its issue, with acceptance criteria coverage, the design decisions the PR implements, and reviewer assignment. Embeds visual proof that was captured beforehand by /validate-implementation (single asset, or a before/after pair for bug fixes) by reading the proof manifest; create-pr is a consumer and does not capture recordings itself. If no proof was captured, it omits the Visual proof section and suggests running /validate-i...

Interview the user to populate the project context files (.sdlc/context/) for a new or empty project. Use when the user says /create-project, "start a new project", "set up project context", "bootstrap an empty project", or wants to fill .sdlc/context/ by answering questions instead of editing stubs by hand.

Record an open question with its context, who can answer it, what it blocks, and when the answer is needed.

Generate a README.md for a project using a structured template with badges, feature lists, roadmap, and setup instructions.

Draft a requirements document with functional and non-functional requirements from a feature brief or issue.

Sequence initiatives across Now/Next/Later horizons, aligned to goals, so prioritization and needs-assessment have a strategic plan to follow.

Define SLOs, SLIs, SLAs, and error budgets for a service so reliability targets are explicit and measurable.

Author a new skill by discovering similar skills, studying their strengths and weaknesses, and synthesizing the best single skill from them. Use when the user says /create-skill, "create a skill", "build a skill", "make a skill for X", or wants a new skill grounded in the best existing examples rather than written from scratch.

Create a technical specification from a requirements document, covering architecture, data models, API contracts, and sequences.

Create great looking SVG diagrams, images, and visualizations as hand-authored SVG following a bundled style guide. Use when the user says "svg", "create an svg image", "svg diagram", "draw this as svg", "architecture diagram in svg", or asks for a figure that needs pixel-level control over layout, color, or branding that Mermaid cannot express. For Mermaid-rendered diagrams use create-mermaid-visualization instead.

Decompose a feature or plan into discrete, actionable tasks with effort estimates and dependencies.

Define a team's Team API (Team Topologies), covering team type, ownership boundaries, services, inputs, outputs, dependencies, and interaction modes with other teams.

Author a team charter defining the team's purpose, vision, stakeholders, responsibilities, roles, operating norms, decision-making, and success metrics as a single artifact.

Define analytics events, success metrics, and telemetry for a feature so usage can be measured from day one.

Create a test plan and test cases covering acceptance criteria, edge cases, and failure scenarios.

Deploy merged changes to the target environment, run smoke tests, and verify the rollback plan.

Generate a profile for a colleague based on their Slack and GitHub activity, covering strengths, weaknesses, interests, avoids, and other relevant information.

Create, view, or update a developer trust profile for a GitHub user. Tracks trust level, strengths, weaknesses, PR patterns, and review history.

Challenge an idea, plan, decision, or argument by constructing the strongest case against it. Use when the user says /devils-advocate, "challenge me", "play devil's advocate", "what am I missing", "steelman the other side", "poke holes in this", or wants stress-testing before committing.

Create a spec directory with specification files per major feature for code in the current directory and its subdirectories.

Write or review documentation following the Divio/Diataxis system, which defines four types: tutorials, how-to guides, reference, and explanation. This is the comprehensive reference skill; create-documentation delegates to this for detailed guidance.

Closes the workday with GitHub and Slack summaries, overall notes, timeline, and next-day standup. Use when the user says /end-day, end of day, EOD, or daily wrap-up.

Closes the month with GitHub and Slack summaries, colleague activity, action items, and thanks. Use when the user says /end-month, end of month, monthly summary, or month wrap-up.

Reflective end-of-day review that forces alignment between your work, your goals, and your team's goals.

Summarize GitHub activity, Slack activity, and overall activity for the day, then generate a standup for the next day.

Reflective end-of-month review covering OKR/goal progress, time allocation trends, team trajectory, and strategic focus adjustments for the next month.

Summarize monthly GitHub activity, Slack activity, colleague activity, and generate a monthly highlights report.

Reflective end-of-week review covering goal progress, time and attention patterns, team health, and what to change next week. Runs the audit-attention skill to classify the week's activities as compounding or depreciating.

Summarize weekly Slack activity, colleague activity, action items, and thanks for the week.

Summarizes the week from Slack, colleagues, action items, and thanks, then runs the end-of-week review. Use when the user says /end-week, end of week, weekly summary, or Friday wrap-up.

Search Slack for messages a set of colleagues authored on a given day, read the full threads behind them, and extract the decisions each of them made plus who supported them, filtering out the chatter and citing permalinks. Use this to catch up on what changed across a team without reading every thread, or when asked "what decisions were made today", "what did <people> decide", "what did my colleagues decide yesterday", or to build a daily decisions digest. Reads the colleague list from the C...

Identify copy-pasted code blocks and near-duplicate logic that should be extracted into shared helpers or modules, ranked by duplication size and churn.

Scan the codebase for functions and modules with high cyclomatic complexity, excessive length, or deep nesting, then produce prioritized refactoring suggestions.

Identify files and modules with missing or insufficient test coverage, ranked by churn and complexity, and suggest what to test first.

Find unused functions, classes, variables, exports, feature flags, and config keys across the codebase and produce a prioritized removal list.

Find public APIs, modules, CLI entry points, and configuration options that lack documentation, ranked by usage and visibility, and suggest what to document first.

Identify functions, methods, and modules missing type annotations in gradually-typed languages (Python, TypeScript, JavaScript), ranked by public visibility and churn.

Orchestrate a bug fix from issue to PR by delegating to reproduce-issue, create-implementation, validate-implementation, and create-pr.

Manages stacked PRs and splits multi-part work into reviewable branches with gh-stack. Use for stack creation, viewing, edits, push, submit, sync, rebase, merge, or checkout; when asked to split or isolate work for review; whenever a user mentions a stack, branch layers, dependent PRs, or gh stack; or when a stack is checked out.

Use ghx as an extended GitHub CLI. It browses issues and pull requests with local disk caching, and performs PR/issue comment operations the standard `gh` CLI does not support: inline PR review comments, line-range comments, thread replies, pending reviews, local comment stashes, and edit/delete of comments. Trigger when the user wants to list/search/view issues or PRs, pre-populate the cache, comment on a PR (especially inline / on a specific file or line), reply to a review thread, manage a...

Generate a Conventional Commits-formatted commit message from only the staged changes, leaving unstaged changes untouched. Use when the user says "commit staged", "commit staged changes", or wants to commit only what is already staged.

Generate a git commit message based on the changes in the repository.

Resolves agents commit SHA and GitHub URL for a skill's SKILL.md, and formats footers for comments or issue bodies posted via gh or ghx. Use whenever a skill posts to GitHub (PR comments, issue comments, issue create, review comments) so readers see which skill and which repo revision produced the content. Other skills reference this instead of duplicating steps.

Pull Google Meet transcripts and Gemini notes from Google Drive and save them as markdown files locally. Use when the user says "pull transcripts", "download transcripts", "sync transcripts", "get meeting notes", or wants to fetch Google Meet transcript or Gemini meeting notes from Drive.

List your open pull requests and their CI status, then fix failing CI across all of them in parallel by fanning out one handle-pr-ci session per failing PR. Use when the user says /handle-failing-pr-ci, "fix my failing CI", "my PRs have failing checks", "get my PRs green", "check my PRs CI", or wants to bulk-fix CI on their own pull requests.

Reply to a comment on a GitHub issue using the codebase, issue description, and comment history as context.

As a PR reviewer, verify that the author's new commits actually address your review comments, resolve fixed threads, reply on partial or unaddressed ones, and evaluate author rebuttals. The reviewer-side counterpart of handle-pr-reviewer-feedback.

Diagnose failing CI checks on a GitHub pull request, fix the root cause, push, and confirm CI passes.

Reply to a comment on a GitHub pull request, implementing changes if appropriate, using the codebase and comment history as context.

Address reviewer comments on your own GitHub pull request, implementing valid feedback or explaining rejections, then push changes. Owns the reviewer-feedback contract (one analysis file per comment at a canonical path, the implement|decline|defer decision vocabulary, and both the analyze-only and execute modes that triage-pr-feedback orchestrates). The author-side counterpart of handle-pr-author-feedback.