Menu
Automatically generate meaningful git commit messages based on staged changes.
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
Reuse one Resend account and one verified sender domain across multiple branded products, especially for solo developers and free-tier portfolios. Use when adding transactional email to another app without creating a separate Resend account or verified domain, while preserving per-product identity, recipients, Reply-To routing, templates, security boundaries, delivery reliability, and awareness of a shared sending quota.
Add captions to a talking-head video. ONE catalog (CATALOG.md) of 32 visual identities behind two engines: column-flow (captions composited INTO the scene — matte occlusion + mix-blend; cream/ink/editorial/keynote/documentary/loud/neon/glitch/chrome/velocity) and themed constitutions (anchor/ordnance/terminal/neonsign/stardust/stomp/scoreboard/transit/vhs/arcade/dossier/laser/thunder/hologram/biolume/aurora/spectrum/papercut/popup/chalkboard/graffiti/brush/inkwater/ransom/lastpage/nightcity — e.g. a glyph-decode climax, a neon sign WRITTEN stroke by stroke, or the quiet `anchor` rail default). Route by identity, never by mode. Trigger on "captions/subtitles", "embed/cinematic captions", "VFX captions", "炸/特效/酷炫字幕", a named identity, or top-tier motion-graphics asks. Embedding every word is wrong for most talking-head content — `anchor` is the verbatim default. Pipeline: transcription → hyperframes remove-background matting → HTML render → ffmpeg overlay. Requires hyperframes and a single-subject clip.
turn arbitrary text — an article, notes, a topic, a brief — into a faceless explainer video, up to ~3 min (sweet spot 30-90s), where every visual is invented (typography, abstract graphics, diagrams, data-viz) rather than captured. There is no URL, no website capture, and no real assets. Use this skill for topic explainers, concept breakdowns, how-tos, listicles, and narrative explainers. Do not use it for a product launch/promo (use /product-launch-video), a tour of a real website (use /website-to-video), a GitHub PR (use /pr-to-video), captions on existing footage (use /embedded-captions), or a short unnarrated motion graphic (use /motion-graphics). If the intent is unclear, route through /hyperframes first. This is the shot-sequence architecture: every frame is authored as a time-coded shot sequence picked from a menu of golden blueprints, so frames develop over their full duration instead of freezing after entrance.
Import Figma content into a HyperFrames composition — rendered assets, brand tokens, components, storyboard sections → animatics (REST/CLI), and Figma Motion animations + shaders (MCP). Use when the user pastes a figma.com link or asks to bring a Figma design, frame, logo, brand, or animation into a video/composition.
All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). HyperFrames-native: single paused timeline, seek-safe, deterministic.
HyperFrames CLI dev loop. Use when running npx hyperframes init, add, catalog, capture, lint, validate, inspect, layout, snapshot, preview, play, render, publish, lambda, doctor, browser, info, upgrade, skills, compositions, docs, benchmark, telemetry, transcribe, tts, or remove-background, or when troubleshooting the HyperFrames build/render environment. Entry point for AWS Lambda cloud rendering (`hyperframes lambda deploy / render / progress / destroy / policies`).
| name | git-commit-generation |
| description | Automatically generate meaningful git commit messages based on staged changes. |
[!NOTE] This skill is based on the Kilo Code Git Commit Generation feature. Attribution: Originally from the Kilo Code Repository.
Generate descriptive commit messages automatically based on your staged git changes. Kilo Code analyzes your staged files and creates conventional commit messages that follow best practices.
{% callout type="info" %}
This feature only analyzes staged changes. Make sure to stage your files using git add or via VS Code interface before generating commit messages.
{% /callout %}
The git commit message generator:
git add or the VS Code git interfaceKilo Code logo next to the commit message field)The generated message will appear in the commit message field, ready for you to review and modify if needed.
{% image src="/docs/img/git-commit-generation/git-commit-1.png" alt="Generated commit message example" width="600" /%}
By default, generated messages follow the Conventional Commits specification:
<type>(<scope>): <description>
<body>
Common types include:
feat: New featuresfix: Bug fixesdocs: Documentation changesstyle: Code style changes (formatting, etc.)refactor: Code refactoringtest: Adding or updating testschore: Maintenance tasks{% tabs %} {% tab label="VSCode" %}
The extension provides the same SCM button in the VS Code Source Control panel. Clicking it generates a commit message using the CLI backend's commit message generation API.
Configuration is handled through the extension's settings or the shared kilo.jsonc config file.
Customize the commit prompt from Settings > Commit Message. Kilo saves this prompt to the current project's config so each repository can follow its own commit conventions without changing your global settings.
You can also set it directly in the project config:
{
"commit_message": {
"prompt": "Write concise conventional commits with the package scope when possible."
}
}
{% callout type="info" %} Git commit message generation is a VS Code extension feature. It is not available in the CLI/TUI. {% /callout %}
{% /tab %} {% tab label="VSCode (Legacy)" %}
You can customize how commit messages are generated by modifying the prompt template:
PromptsPrompt template to match your project's conventions{% image src="/docs/img/git-commit-generation/git-commit-2.png" alt="Commit message generation settings" width="600" /%}
The default template creates conventional commit messages, but you can modify it to:
You can configure which API profile to use for commit message generation:
Prompts settings, scroll to "API Configuration"{% callout type="tip" %} Consider creating a dedicated API configuration profile with a faster, more cost-effective model specifically for commit message generation. {% /callout %}
{% /tab %} {% /tabs %}
git add -p for partial file staging when neededHere are examples of messages the feature might generate:
feat(auth): add OAuth2 integration with Google
Implement Google OAuth2 authentication flow including:
- OAuth2 client configuration
- User profile retrieval
- Token refresh mechanism
fix(api): resolve race condition in user data fetching
Add proper error handling and retry logic to prevent
concurrent requests from causing data inconsistency
docs(readme): update installation instructions
Add missing dependency requirements and clarify
setup steps for new contributors
If the button doesn't appear or generation fails, ensure you have staged changes:
git add <files>
# or stage all changes
git add .
If generated messages aren't helpful:
The feature integrates with VS Code's built-in git functionality. If you encounter issues: