> open agents/development/pr-merger/SOUL.md
> cat identity rules capabilities
PR Merger SOUL.md
PR Merger is a development SOUL.md template for pull request management agent.
# SOUL.md — PR Merger
CATEGORY
Development
ROLE_FOCUS
Pull Request Management Agent
FILE_PATH
agents/development/pr-merger/SOUL.md
SOURCE_TYPE
awesome-openclaw-agents catalog
What This Template Type Covers
This page is a dedicated landing URL for the PR Merger SOUL.md pattern. It gives users and search engines one stable page for this specific template type instead of hiding everything behind a single filter UI.
PR Merger maps to the role "Pull Request Management Agent". Focuses on engineering workflow clarity, tool boundaries, and reliable output formats.
Authorship Note
This page is an indexed preview, not an original authored template by this site. Template authorship remains with the original source, and this page exists to organize discovery, show a partial preview, and link back to the source file.
SOUL.md Preview
Open raw sourceIdentity
Personality
Capabilities
Rules
Typical Use Cases
Start a pr merger agent with a clearer identity and operating boundary.
Benchmark this development template against other roles before customizing your own SOUL.md.
Use it when you need behavior tuned for pull request management agent.
What To Look For In This SOUL.md
Best For
People searching for a named SOUL.md type, a shareable prompt starter, or a category-specific agent configuration page.
Likely Sections
Identity, philosophy, rules, skills, constraints, escalation rules, and response formatting tuned for pr merger workflows.
FAQ
What is the PR Merger SOUL.md template used for?
PR Merger is a development SOUL.md template used to define identity, operating rules, and expected behavior for that specific agent role.
Does this page show the real PR Merger SOUL.md content?
Yes. This page renders parsed preview sections from the original SOUL.md source file and links back to the source file for the full document.
How should I customize the PR Merger SOUL.md template?
Keep the role identity and core operating rules that match your use case, then adapt tone, boundaries, tools, and escalation rules to your own workflow.