メニュー
Git commit with conventional commits, optional draft PR. Small, incremental, human-written messages. Never mentions AI, agents, or Claude. Use when: commit, commit this, save changes, git commit, stage and commit, create PR, open PR, draft PR.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Ghostwriter, tutor and reviewer for Leandro's technical blog articles (leandronsp.com). Leandro writes 100% of the article, never the assistant. The assistant explains the underlying concepts (physics, math, CS), hands over passages to copy and adapt, reviews concisely, and standardizes structure (agenda, anchors, conclusion). Use when the user says "ghostwriter", "me ajuda no artigo", "revisa o artigo", "help me write", "tô escrevendo um artigo", "seja meu ghostwriter", "tutor do artigo", or is drafting a post in DevTUI.
Search and retrieve notes from the Obsidian vault. Use when the user wants to find notes, recall past ideas, get context on a topic, look up references, browse blog drafts, get live stream ideas, consolidate notes for writing, or load knowledge from their second brain into the conversation. Trigger on phrases like "check my notes", "what do I have on", "find in vault", "search notes", "load notes about", "bring me everything about", "consolidate", "briefing for", "ideia pra live", "what should I stream".
Create a standalone, self-contained interactive HTML explainer in an editorial style (deep navy canvas, one accent, hairlines, mono microtype) for a technical change, architecture decision, incident, data flow, or product behavior. Ships with Present mode (a keyboard-driven slide deck). Works in any project, any stack. Use when the user says "explainer", "create an explainer", "explain this visually", "make a shareable page", "interactive explainer", "write this up as a page", or "turn this into an explainer".
Automatically extract text from images using Tesseract when the model doesn't support images. This is a pi extension that hooks into before_agent_start and runs OCR transparently. No manual triggering needed. Only activates on vision-free models. Do NOT trigger manually — the extension handles it automatically.
Answer questions about personal finances by searching only the ~/vault/finance/ section of the Obsidian vault. Use when the user asks "quanto gastei", "como estou em [mês]", "qual minha despesa fixa", "posso gastar X", "forecast", "carteira", "minha situação financeira", or any question about their money, bills, cards, or investments.
Process credit card bills, bank statements, or screenshots, extract expenses, update current month snapshot and 6/12-month forecasts in the Obsidian finance vault. Use when the user shares faturas, extratos, prints, or asks to "atualizar finanças", "processar contas", "atualiza fatura", "roda forecast", "atualiza mês". Writes ONLY to ~/vault/finance/.
| name | commit |
| description | Git commit with conventional commits, optional draft PR. Small, incremental, human-written messages. Never mentions AI, agents, or Claude. Use when: commit, commit this, save changes, git commit, stage and commit, create PR, open PR, draft PR. |
Small, incremental git commits following conventional commits. Optionally open a draft PR.
/commit - commit staged changes/commit detailed - multi-paragraph commit/commit --pr - commit + open/update a draft PR<type>(<scope>): <short description>
Types: feat, fix, refactor, test, chore, docs
Scope: optional, module or area name (e.g. feat(auth): add token refresh)
Single-line commit message.
git commit -m "feat(auth): add token refresh"
detailed or when the change is significant)Multi-paragraph for milestone features, non-obvious fixes, architectural changes.
Output the proposed message as plain text for review. Do NOT run git commit until the user approves.
git commit -m "feat(auth): add token refresh on expiry
Tokens are now refreshed automatically when they expire.
Refresh failures fall back to re-authentication instead of
silently failing the request."
git add <files>, never git add -A or git add .Before committing, run the project's test suite. Check what's available:
# Try common test commands
make test 2>/dev/null || mix test 2>/dev/null || cargo test 2>/dev/null || bundle exec rspec 2>/dev/null || npm test 2>/dev/null
Check the diff before staging:
git diff
git diff --staged
test(auth): add token expiration edge cases
feat(api): add webhook endpoint for events
fix(worker): handle nil payload on retry
refactor(store): extract state operations into module
docs(readme): add setup instructions for local dev
chore(ci): add type checking to CI pipeline
--pr)When called with --pr, commit any pending changes first, then open or update a draft PR.
git branch --show-current
Never commit to main/master unless explicitly requested. If on main, create a feature branch:
git checkout -b <type>/<short-name>
Branch naming follows the commit type: feat/, fix/, refactor/, test/, chore/, docs/.
Commit any uncommitted changes before proceeding.
git log main..HEAD --oneline 2>/dev/null || git log master..HEAD --oneline
git diff main...HEAD --stat 2>/dev/null || git diff master...HEAD --stat
Check conversation context, branch name, or commit messages for issue references (GitHub #N or Linear TEAM-N). If found, link it in the PR body with a closing keyword.
gh pr view --json number,title,body 2>/dev/null
Show the proposed title and body to the user. Wait for approval before creating.
<type>: <short description>
Same rules as commits: lowercase, imperative, under 70 chars.
If a Linear ID is available: TEAM-123 - <type>: <short description>
Two sections only. No checklists, no file lists, no templates.
<issue_url>
### Background
1-2 paragraphs explaining the problem and the high-level approach.
Write naturally, like explaining to a colleague.
### Key Decisions
1. **Decision title**: brief explanation of the choice.
2. **Another decision**: what was done, stated as a fact.
Link the issue URL on its own line (no "Closes" keyword). Omit if no source issue. Omit Key Decisions if there are none worth mentioning (small fixes).
New PR:
gh pr create --draft --title "<title>" --body "<body>"
Existing PR:
gh pr edit --title "<title>" --body "<body>"
Push the branch first if needed:
git push -u origin $(git branch --show-current)
Report the PR URL to the user.