Skip to content

Automattic/wordpress-atmosphere / .agents/skills/pr

INVOKE THIS SKILL before creating any PR to ensure compliance with branch naming, changelog requirements, and reviewer assignment.

ATmosphere PR Workflow

Quick-reference for opening a PR. Full reference: docs/pull-request.md.

Branch Naming

PrefixUse
add/{feature}New feature.
update/{feature}Iterating on an existing feature.
fix/{bug}Bug fix.
try/{idea}Experimental — open as draft.

Reserved: release/{X.Y.Z} (owned by the release script), trunk.

git checkout trunk && git pull origin trunk
git checkout -b fix/something

Required Before Opening

  1. Lint + tests must pass.

    composer lint
    npm run env-test
    
  2. Changelog entry or Skip Changelog label.

    composer changelog:add
    

    Commit the entry on the same branch as the code change. End the message with punctuation. Write for end users — no class names, no internal jargon.

    If neither a changelog entry nor a Skip Changelog label applies, stop and ask the user which they prefer. Don't open the PR with neither.

  3. Code review. Delegate the diff to the code-review agent. Address every critical finding before opening the PR.

Opening the PR

# Create PR (includes required assignment/reviewer).
gh pr create --assignee @me --reviewer Automattic/atmosphere

Copilot is requested as a reviewer automatically by the trunk branch ruleset — don't add it manually.

Use .github/PULL_REQUEST_TEMPLATE.md as-is — don't invent custom formatting. The body must include:

  • Summary explaining why (not just what — the diff covers that).
  • Testing instructions a reviewer can reproduce locally.
  • Screenshots for any visual change (before / after).

Changelog Messages

Write for end users; they appear in the WordPress update screen.

✅ Fix posts not appearing on Bluesky when published via Quick Edit.
✅ Add option to disable standard.site document records.
❌ Refactor Publisher class to handle edge case in applyWrites batch.
❌ Fix TID collision in transformer output.

End with punctuation. Never mention AI tools or coding assistants.

When to Read the Full Docs

Read docs/pull-request.md when you need:

  • The full pre-PR checklist (code preparation, testing, documentation, review).
  • Commit message format (the Type: prefix table).
  • Special situations — Hotfix, Breaking Change, New Feature, Bug Fix, Experimental, Multi-PR Feature checklists.
  • Common review feedback patterns — what reviewers typically ask for and how to respond.
  • Label reference.

Related Skills

  • release — release script, patch releases, GitHub Release UI.
  • dev — running tests, linting, troubleshooting wp-env.
  • code-style — PHP conventions the reviewer will be checking against.
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 466kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 196kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 196kUpdated Claude CodeCodexVerifiedInstall