pragmatic-engineer
@pragmatic-engineer Organization
Public Skills
delegating-subagents
by pragmatic-engineer
Handoff, roster, routing, and recovery rules for subagents. Use before dispatching any subagent, and when one finishes or goes quiet.
systematic-debugging
by pragmatic-engineer
Root-cause-first debugging. Use on any bug, failing test, or unexpected behavior, before proposing a fix.
engineering-standards-python
by pragmatic-engineer
Python rules for code and reviews, covering style, idioms, types, errors, async, testing, packaging, security and the Ruff rules that check them. Use when writing or reviewing Python, or a diff that touches .py or .pyi files.
engineering-standards
by pragmatic-engineer
Team standards for code design, commits, PRs, testing, and deployment. Use when designing code, preparing a PR, or planning tests or a deploy.
engineering-standards-rust
by pragmatic-engineer
Rust rules for code and reviews, covering ownership, errors, types, API design, async, unsafe, testing and Clippy lints. Use when writing or reviewing Rust, or a diff that touches .rs files.
grounding-review
by pragmatic-engineer
Evidence and labeling rules for reviewing a PR or diff. Use for any quick or deep code review. Not for investigation.
playbook-usage
by pragmatic-engineer
Lists /playbook:* commands and when to use each. Use when asked what the plugin does or which command fits a task.
writing-style
by pragmatic-engineer
"One plain, simple-English standard for prose a human reads: chat, PR descriptions, commit messages, review comments, tickets, Confluence, Slack, ADRs. Cuts filler, binary contrasts and dashes. Use before writing or posting any."
finish-pull-request
by pragmatic-engineer
Self-reviews a freshly opened PR, fixes findings, promotes the draft, merges when allowed. Use right after create-pull-request returns a PR URL.
atlassian
by pragmatic-engineer
Use when reaching Jira work items, Confluence pages or Teamwork Graph data, choosing between the Atlassian MCP server, acli and twg, or when /playbook:learn-project or a ticket-driven plan needs Atlassian access.
engineering-standards-javascript
by pragmatic-engineer
JavaScript and TypeScript rules for code and tests, including validation and Jest or Vitest mocks. Use when writing or reviewing JS or TS.
grounding-research
by pragmatic-engineer
Evidence rules for investigating code (cite file:line). Use when exploring a codebase, tracing execution, or mapping dependencies. Not for PR review.