Skip to content

dedalus-labs/wingman / .agents/skills/promote

promote

Verified

Create a changelog-style promotion PR between two branches. Use for release promotions or branch-to-branch merges with a structured changelog.

Context (auto-detected)

  • Commits to promote: !git log --oneline origin/main..HEAD 2>/dev/null || echo "(no commits ahead of main)"

Rules

  • Default: promote current branch → main
  • --from <branch> overrides source (default: current branch)
  • --to <branch> overrides target (default: main)
  • --dry-run prints the PR body without creating it
  • Commits are grouped by conventional commit type into changelog sections

Changelog Sections

PrefixSection
featFeatures
fixBug Fixes
refactorRefactors
perfPerformance
testTests
docsDocumentation
chore, ciChores

Unrecognized prefixes go under Chores.

Task

  1. Parse $ARGUMENTS for --from, --to, --dry-run
  2. Fetch the latest from origin for both branches
  3. Get the commit list: git log --format="%H %s" origin/<to>..origin/<from>
  4. If no commits, report that target is up to date and stop
  5. Build the changelog body:
    • Group commits by section using the table above
    • Each bullet: * **scope:** description ([short-hash](commit-url)) or * description ([short-hash](commit-url)) if unscoped
    • Include a "Full Changelog" comparison link
    • Order sections: Features, Bug Fixes, Refactors, Performance, Tests, Documentation, Chores
  6. If --dry-run, print the body and stop
  7. Create the PR via gh pr create --base <to> --head <from> --title "chore(release): promote <from> → <to>" --body "..."
  8. Return the PR URL
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: 469kUpdated 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: 197kUpdated 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: 197kUpdated 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: 197kUpdated Claude CodeCodexVerifiedInstall