pr-to-main-cleanup
This Claude Code skill automates the cleanup of feature branches after they are merged into the main branch via pull request. It switches to main, pulls the latest changes, then deletes both the local and remote feature branches using force deletion, which is necessary since squash merges prevent git from automatically detecting merge status. Use this when a user requests branch cleanup or deletion after completing a PR merge.
git clone --depth 1 https://github.com/breaking-brake/cc-wf-studio /tmp/pr-to-main-cleanup && cp -r /tmp/pr-to-main-cleanup/.claude/skills/pr-to-main-cleanup ~/.claude/skills/pr-to-main-cleanupSKILL.md
# PR to Main Cleanup Delete merged feature branches after PR is merged to main. ## Workflow 1. **Gather context** (parallel): - `git branch` to identify current branch - `git log --oneline -1` to confirm current state 2. **Execute cleanup**: - Switch to main branch - Pull latest changes from origin - Delete local feature branch - Delete remote feature branch ## Commands ```bash git checkout main && git pull origin main && git branch -D <branch-name> && git push origin --delete <branch-name> ``` ## Important Notes - PRs to main are always squash-merged, so use `-D` (force delete) since git cannot detect squash merges as "merged" - Always pull latest main before deleting to sync merge status
Jiraチケットの要件とConfluenceの関連ドキュメントを基に、Frontend/Backend/Infrastructureに分割した実装計画を策定するプランニングスキル。Jiraチケット情報とConfluence検索結果が前段で取得済みであることを前提とし、構造化された実装計画を出力する。「プランニング」「実装計画策定」「タスク分割」などの文脈で使用。
Analyze PR review comments from a GitHub PR URL. Fetch review comments, verify each finding against the actual codebase, assess validity (correct/incorrect/partial), present a structured summary with recommended actions, and optionally reply to each comment on GitHub. Use when given a PR review URL or when asked to check/analyze PR feedback.
Create a PR to the main branch for feature/fix changes in this pnpm + Changesets monorepo. Use when the user says "PRを作成", "mainにPR", or wants to submit changes for review. Always run this in the monorepo-aware way — identify the affected package(s) and make sure a changeset exists, because the release pipeline is Changesets-driven.
Use when modifying `resources/workflow-schema.json` in cc-wf-studio to influence how AI agents generate workflows via the cc-workflow-ai-editor skill. Triggers include "AIが特定のノードタイプを選んでくれない", "ワークフロー生成のバイアスを調整したい", "スキーマの description を変えたい", "新しいノードタイプを追加したい", "嘘の制約がスキーマに混じっていないか確認したい". Covers what the schema actually does (instructions to AI, not runtime constraints), the design philosophy (align direction, do not prescribe rules), the build pipeline (.json → .toon auto-generated), and known bias sources to audit.
AI workflow editor for CC Workflow Studio. Create and edit visual AI agent workflows through interactive conversation using MCP tools (get_workflow_schema, get_current_workflow, apply_workflow, update_nodes). Use when the user wants to create a new workflow, modify an existing workflow, or edit the workflow canvas in CC Workflow Studio via the built-in MCP server.
Use the `ccwf` CLI (from @cc-wf-studio/cli) to render, validate, preview, export, or run cc-wf-studio workflow JSON files from the terminal. Apply whenever the user mentions viewing, visualizing, checking, executing, or converting a workflow under `.vscode/workflows/` (or any `*workflow*.json`), wants a Mermaid diagram of a workflow, asks to "see" / "preview" / "open" a workflow, or wants to run a workflow as a Claude Code Skill without opening VSCode.