.claude/skills/merge-approved-prs/SKILL.md
Use when the user wants to merge all PRs they have approved - updates each branch from main, waits for CI checks to pass, merges, then summarizes results
npx skillsauth add department-of-veterans-affairs/vets-design-system-documentation merge-approved-prsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Runs the scripts/merge-approved-prs.sh script to batch-merge all open pull requests that the current user has approved on the vets-design-system-documentation repository.
Announce at start: "Running merge-approved-prs to batch-merge your approved PRs."
Trigger phrases:
If the user hasn't explicitly passed flags, you may ask:
If no preference is stated, use the defaults (merge commit, delete branch).
Always invoke via bash to work around GFE execution policy:
bash scripts/merge-approved-prs.sh
Common variations:
# Squash merge instead of merge commit
bash scripts/merge-approved-prs.sh --squash
# Keep branches after merge
bash scripts/merge-approved-prs.sh --no-delete-branch
# Preview without making any changes
bash scripts/merge-approved-prs.sh --dry-run
# Increase timeout for slow CI (default 900s = 15 min per PR)
bash scripts/merge-approved-prs.sh --timeout 1800
The script is fully autonomous — it will:
gh pr update-branch to merge main into the PR branchgh pr checks every 15 seconds until all checks pass or failgh pr merge if checks pass; skip if they failgit pull origin main to update your local mainIf any PRs fail, report them clearly:
--timeoutgh CLI (already authenticated as humancompanion-usds)reviewDecision is CHANGES_REQUESTED (any reviewer requested changes) are excludeddocumentation
Use when making documentation changes in the doc-queue workflow, writing new component/pattern/template guidance, or updating existing VADS documentation - ensures compliance with VADS templates and style standards
testing
Creates and standardizes Mermaid decision flowcharts in VA Design System documentation, including templates, node types, accessibility alternatives, and the standard Jekyll include pattern.
documentation
Use after selecting a documentation issue from the doc-queue to groom it - analyzes the issue, identifies gaps, prompts the designer for clarity, and posts a structured grooming comment so the issue is ready for the writing-vads-guidance skill or an async agent
documentation
Use when a designer asks to work on guidance or documentation issues, process documentation queue, or close out doc tickets - fetches oldest issue from quarterly epic and guides through resolution