Menú
Commit, git commit message, or staged changes summary. Use by github agent only when the user explicitly requests a commit.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
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.
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.
Weekly content generation, content ideas from week, repurpose recent notes, or content calendar. Use when the user asks what to post from recent work or wants LinkedIn/article ideas from vault notes.
| name | commit |
| description | Commit, git commit message, or staged changes summary. Use by github agent only when the user explicitly requests a commit. |
Use only when the user explicitly requests a commit.
Before committing:
git status.git diff and staged diff.Use this subject format unless the repository has a clear different convention:
<type>(<scope>): <imperative summary>
Allowed types:
feat — user-visible featurefix — bug fixrefactor — behavior-preserving code restructuringdocs — documentation onlytest — tests onlychore — maintenance/config/toolingperf — performance improvementbuild — build/dependency changesci — CI workflow changesOptional body template:
Why:
- <reason for change>
Verification:
- <commands run and result>
Never commit secrets, unrelated files, or unverified broad rewrites.