From claude-resources
Creates a GitHub Actions workflow that auto-merges a production branch into a documentation branch, keeping a doc deploy branch in sync without manual intervention.
How this skill is triggered — by the user, by Claude, or both
Slash command
/claude-resources:dev-gh-actions-doc-auto-mergeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create a GitHub Actions workflow that automatically merges a production branch into a documentation deploy branch, keeping docs up-to-date without manual sync.
Create a GitHub Actions workflow that automatically merges a production branch into a documentation deploy branch, keeping docs up-to-date without manual sync.
Ask the user to confirm (use AskUserQuestion):
doc)main)Look for existing sync workflows in .github/workflows/ to avoid duplicates.
Create .github/workflows/sync-<production>-to-<doc>.yml:
name: Sync <production> to <doc> branch
# <production>ブランチへのpush時に<doc>ブランチへ自動マージ
# ドキュメントサイトが常に最新の<production>の内容を反映するようにする
on:
push:
branches: [<production>]
permissions:
contents: write
jobs:
sync:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
ref: <doc>
fetch-depth: 0
- name: Merge <production> into <doc>
run: |
git config user.name "github-actions[bot]"
git config user.email "github-actions[bot]@users.noreply.github.com"
git merge origin/<production> --no-edit
- name: Push
run: git push origin <doc>
Replace <production> and <doc> with the confirmed branch names.
After creating the workflow file, remind:
on.push.branches target) for GitHub Actions to pick it upnpx claudepluginhub takazudo/claude-resources --plugin claude-resourcesRuns verification checks, reviews the diff, picks the integration path (merge, PR, squash, stacked PR), writes the PR/merge message, pushes, and cleans up branches and worktrees.
Guides Git branching strategies (GitHub Flow, trunk-based, GitFlow), commit conventions, merge vs rebase, conflict resolution, and collaborative development best practices.
Applies GitHub Flow: short-lived feature branches, PRs with passing CI, deploy immediately on merge. Keeps main deployable for continuous deployment teams.