github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
What this skill does
# GitHub Pull Request Workflow Ship a PR a reviewer can land without follow-up clarifying questions. The aim is high signal in the title and body, evidence the change works, and clean replies when feedback comes in. ## When to use - You are about to open a PR for a change that is functionally complete. - A reviewer left comments and you need to respond and push fixes. - A PR has been open more than a day and needs to be brought back into shape (stale conflicts, missing description, missing verification). ## When not to use - The change is not yet functionally complete. Finish the work first; draft PRs that bounce on review are noise. - The repository uses a non-GitHub forge. Adjust to that forge's conventions; do not force GitHub-isms. ## Branch hygiene before opening - Rebase or merge from the target base so the diff is current. - Squash WIP commits into reviewable units. Prefer one commit per logical change; do not force one-commit-per-PR if the work is genuinely multi-step. - Confirm tests, typecheck, and lint pass locally. Note any deliberate skips in the PR body. - Remove debug prints, commented-out code, and `TODO` markers that are not tracked. ## PR title - Imperative mood, under 70 characters. - Lead with the user-visible change, not the file touched. `Allow CSV export from reports table` beats `Update reports.tsx`. - If the repo uses an issue prefix convention (`PAP-1234:`, `[security]`), follow it. - No trailing period. ## PR body Use this structure: ```md ## Summary - 1–3 bullets describing what changed and why. ## Implementation notes - Anything non-obvious in the diff: trade-offs, dropped alternatives, gotchas. - Migration or config implications. ## Verification - The exact commands or steps you ran. - Screenshots or short clips for UI changes (required if pixels moved). - Edge cases you exercised by hand. ## Risk and rollback - What breaks if this is reverted, and how to revert cleanly. ``` Skip the `Risk and rollback` section only for clearly trivial PRs (typos, docs). ## Verification evidence - Tests passing in CI is necessary, not sufficient. Reviewers also need to know the change behaves correctly end to end. - For UI work, include screenshots of the golden path and one edge case. Tag dark and light mode if the project supports both. - For migrations, include a dry-run plan and reversal steps. - For performance changes, include a before/after measurement, not adjectives. ## Replying to review comments - Reply on every comment, even with just "fixed in <commit-sha>" — silent fixes leave the reviewer guessing. - Push fixes as new commits while review is active; do not amend during review unless the reviewer agrees. - If you disagree with feedback, say so with one sentence of rationale and let the reviewer decide. Don't escalate over comments. - Re-request review explicitly after pushing changes. ## Merge checklist - All required checks green. - All review comments resolved. - PR title/body still accurate (update if scope changed mid-review). - Linked issue moves to `in_review` or `done` per project convention. - Delete the branch after merge unless it is a long-lived integration branch. ## Anti-patterns - PR description that says "see commits". Reviewers should not need to read the log. - Mixing refactor and behavior change in the same PR with no separation in the body. - "Address feedback" commits that bundle unrelated edits. One commit per round of feedback is fine; one commit for everything in flight is not. - Force-pushing during active review without telling the reviewer.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.