ワンクリックで
pr-management
Use in the Release phase to commit, branch, PR, and sync. Only plugin files go to main — everything else stays on dev.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use in the Release phase to commit, branch, PR, and sync. Only plugin files go to main — everything else stays on dev.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when creating a local agent for a pas-clief workspace. Walks the user through naming the agent, defining its role, listing its skills, and writing CLAUDE.md and CONTEXT.md from templates. The agent lands in `library/agents/<name>/`.
Use when drafting and publishing a newsletter issue. Walks research → draft → publish phases, using the writer agent. Example library process for pas-clief — copy or extend it for your own use.
Use when applying a workspace's drafting conventions to written output — voice, format, sentence rhythm, the things that make output feel like it belongs to this project. Reads the workspace's style notes if any and adjusts the draft accordingly.
Use when line-editing a draft for clarity and economy. Tightens sentences, removes filler, rewrites awkward constructions, ensures every sentence earns its keep. Apply this skill on the final pass before output.
Use when an agent needs to gather sources or background information from the web for a topic. Produces a concise sources file with URLs, summaries, and the most relevant excerpts.
Use when checking that a pas-clief workspace is current with the latest plugin conventions, or when migrating from an older version. Walks a checklist of structural and template changes and offers to apply each.
| name | pr-management |
| description | Use in the Release phase to commit, branch, PR, and sync. Only plugin files go to main — everything else stays on dev. |
main — Plugin distribution only. Contains plugins/pas/ and nothing else.dev — Development workspace. Everything lives here: processes, workspace, library, feedback, plans.PRs target main and contain only plugins/pas/ files. Dev artifacts never leave dev.
After Validation passes and the product owner approves release.
Before committing, bump the patch version:
bash plugins/pas/hooks/lib/bump-version.sh
This updates plugins/pas/.claude-plugin/plugin.json and .claude-plugin/marketplace.json in place. Include both files in the plugin commit below.
Create two commits on dev:
Plugin commit — files under plugins/pas/ plus the marketplace catalog:
git add plugins/pas/... .claude-plugin/marketplace.json
git commit -m "{descriptive message}"
Dev artifacts commit — everything else (workspace, feedback, .gitignore, etc.):
git add .gitignore workspace/ processes/ library/ ...
git commit -m "Cycle-{N} dev artifacts: {brief summary}"
Push dev: git push origin dev
git checkout main && git pull origin main
git checkout -b {branch-name} main
git cherry-pick {plugin-commit-hash}
If cherry-pick conflicts (modify/delete for files new to main), resolve by keeping the modified version:
git add {conflicted-files}
git cherry-pick --continue --no-edit
Branch naming: Use the primary change as the branch name, e.g., fix/feedback-deletion-workspace-utility.
git diff main --stat
Every file in the diff MUST be under plugins/pas/ or .claude-plugin/. If any other file appears, abort and fix.
git push -u origin {branch-name}
gh pr create --base main --title "{title}" --body "{body}"
PR body format:
## Summary
- {bullet points describing changes}
## Test plan
- [ ] {verification items from validation report}
Issue linking: Use "closes #N" in the PR body for issues this fixes. Comment on the issue with root cause and fix reference.
After the product owner merges the PR on GitHub:
git branch -d <feature-branch>
After the PR is merged on main, sync main back into dev so that merge commits and any squash diffs are reflected:
git checkout dev
git fetch origin main
git merge origin/main --no-ff -m "Merge main into dev after PR #{N}"
Immediately verify protected directories survived the merge:
# Under PAS 1.4.0+ pas-development lives INSIDE the plugin tree (authoritative).
test -f plugins/pas/processes/pas-development/process.md && echo "OK: pas-development process.md" || echo "MISSING: plugins/pas/processes/pas-development/process.md"
# Consumer-side workspace (cycle state) stays in .pas/workspace/.
test -d .pas/workspace/ && echo "OK: .pas/workspace/" || echo "MISSING: .pas/workspace/"
If any are missing, restore them from the commit before the merge:
git checkout HEAD~1 -- plugins/pas/processes/pas-development/ .pas/workspace/
git commit -m "Restore protected directories after main merge"
This step is required. Skipping it causes dev and main to diverge, and the next cherry-pick becomes harder. The verification guard prevents the class of bug that has deleted plugins/pas/processes/pas-development/ (formerly processes/pas-development/) twice in the past — the path moved in cycle-15 but the protection stays.
plugins/pas/ and .claude-plugin/ files