Menu
Create-pr, pull request, or PR body. Use by github agent when the user explicitly requests a PR.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use this skill when the user asks to analyze, create, or update an investment asset/company in Notion Assets / Investments. Produces professional-grade, evidence-backed asset research and then creates or updates the matching Notion asset page after confirmation.
Cartography, deep codebase map, repo map, onboarding map, or navigation index. Use for explicit codebase mapping/onboarding requests that need multiple cartography subagents and docs/indexes.
Comment code, explain functions, or add documentation comments. Use to make code understandable after implementation.
Commit, git commit message, or staged changes summary. Use by github agent only when the user explicitly requests a commit.
Medium article, long-form article, essay, or article from notes. Use when the user asks to create/write a Medium-style article using Content Vault evidence, positioning, and humanization rules.
LinkedIn post, social post, short content draft, or post from notes. Use when the user asks to write/create a LinkedIn/social post using the Content Vault voice, evidence, and anti-AI-writing rules.
| name | create-pr |
| description | Create-pr, pull request, or PR body. Use by github agent when the user explicitly requests a PR. |
Use only when the user explicitly requests a PR.
Use the same style as commits:
<type>(<scope>): <imperative summary>
## Summary
- <1-3 bullets describing the outcome>
## Changes
- <main implementation changes>
- <docs/config/test changes>
## Verification
- `<command>` — <what it proved>
## Risks / Rollback
- <known risks, migrations, feature flags, rollback path>
## Tests
- <tests passed, failed, or skipped>
## Links
- <issues, tasks, docs, screenshots for UI if relevant>
Before PR: