Menu
Guide for creating commit message. This skill should be used when you try to create a commit message.
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
| name | commit-message |
| description | Guide for creating commit message. This skill should be used when you try to create a commit message. |
| license | MIT |
Format: <type>(<scope>): <subject> (max 120 chars, lowercase subject, no period)
Types: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert
Common Scopes: admin, collections, ui, components, store, filters, scraper, types, ai, omdb, youtube, search, db, data, api, config, deps
Multi-Scope: Choose primary scope for changes spanning multiple areas. Split unrelated changes into separate commits. Omit scope for global changes.
Rules:
Closes #123Body (optional): Add blank line after subject, then explain what/why (not how). Body lines max 120 chars. Use for complex changes needing context.
Examples:
feat(scraper): add youtube channel scraping
fix(validation): handle missing imdb ids correctly
feat(enrichment): add omdb api integration
Integrate OMDB API to enrich movie metadata.
Closes movies-deluxe-uq0.12
Breaking Changes: Add BREAKING CHANGE: in footer
One sentence about this skill. Use this skill when: "keyword1" "keyword combination"
Guide for verifying frontend changes using chrome-devtools MCP. Use this when you need to verify UI changes, check for console errors, or test frontend functionality after making changes to Vue components, pages, or styles.
Rules for vue component setup. Use this when writing a new vue component or when reviewing an exisinging component.
Guide for checking and fixing Nuxt 4 auto-import usage. Use this when reviewing impors in Vue components, composables, or TypeScript files in a Nuxt 4 project.