Menu
Create consistently named git branches.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use when onboarding an agent into an existing project in the orst vault.
Generate a Codex Super Bowl merch redemption URL (tokenized) and open it. Use when a user asks to redeem Super Bowl/Codex merch, needs a redemption token, or wants the merch redemption link.
Capture conversations and decisions into structured Obsidian notes; use when turning chats or ad hoc notes into durable wiki/how-to/decision artifacts.
Prepare and run meetings with Obsidian context; use when building agendas, pre-reads, and post-meeting notes linked to existing vault knowledge.
Research across Obsidian notes and synthesize structured documentation; use when producing briefs, comparisons, and reports with note-level citations.
Turn Obsidian specs into implementation plans and execution tasks; use when converting PRDs or feature notes into linked plans, task notes, and status tracking.
| name | git-branch |
| description | Create consistently named git branches. |
| license | MIT |
| compatibility | opencode |
| metadata | {"audience":"maintainers","workflow":"github"} |
Use this when you are preparing to create a new branch in a git repository.
Naming convention: <context>/[issue-number-]<short-description>
Contexts:
chore: non-code tasks like dependency bumpsdoc: documentation changesfeat: new featuresfix: bug fixesref: refactoring without functionality changesrfc: RFC design documentsrelease: preparing a release.Examples:
feat/1234-user-authenticationfix/5678-memory-leakdoc/improve-readmeRequirements:
master