Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

git-hero-gitmoji

Estrellas4

Forks0

Actualizado9 de julio de 2026 a las 23:51

Selects and applies gitmoji emoji prefixes for Git commit messages, integrated with Conventional Commits format. Use when the user asks about gitmoji, wants an emoji for a commit message, asks 'which emoji for...', 'quel emoji pour...', mentions commit emoji conventions, says 'prefix my commit', 'gitmoji for', 'emoji commit', or wants to decorate commit messages with standardized emoji. DO NOT USE when: the user wants plain Conventional Commits with no emoji; general Git help → use git-hero-git-guru.

Instalación

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.

Ejecutar en Manus

Fuente

bsene

bsene/skills

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

Explorador de archivos

2 archivos

SKILL.md

readonly

Más de este repositorio

mismo repositorio

simple

bsene/skills

Use this skill whenever writing new code, proposing a bugfix, reviewing a PR/diff, or discussing whether to add an abstraction, config layer, plugin system, or generic mechanism. Also trigger for architecture/design discussions, is this too complex" questions, or any point where Claude is about to suggest introducing a new abstraction layer. The core stance — code is written for humans to read, not as an artwork to admire — optimize for affordance (like a road sign, instantly readable) rather than elegance or cleverness. Trigger even if the user doesn't name "simplicity" explicitly — e.g. "should I make this configurable", "quick fix for this bug", "review this PR", "should I abstract this into a helper", "this codebase feels messy".

2026-07-264

typescript

bsene/skills

TypeScript-specific best-practices and rule enforcement — type safety, runtime validation, error handling, and TS-only conventions. Routes to type-system and Zod sub-skills, the `javascript` skill for JS-foundation rules, and `oop-principles` for design patterns and SOLID. TRIGGER when: language (TypeScript, TS, .ts, .tsx, idiomatic TypeScript), type-system (discriminated unions, generics, utility types, make illegal states unrepresentable, type narrowing), safety (strict mode, any vs unknown, ts-expect-error, ts-ignore, type assertions), runtime (Zod, schema validation, runtime type checks, parse/safeParse), errors (error handling without throwing, union return errors, Result type), ts-conventions (readonly modifier, return type annotations, interface prefix, `as const`), contracts (domain vs DTO, monorepo types, API contract types). DO NOT USE when: user asks generic JS questions with no TS angle — use `javascript` instead.

2026-07-264

typescript-type-system

bsene/skills

Deep dive into TypeScript's type system — narrowing, discriminated unions, mapped types, conditional types, type guards, branding, and escape hatches. TRIGGER when: user asks about unknown vs any, type narrowing, discriminated unions, exhaustiveness checking, mapped types, conditional types, infer keyword, user-defined type guards, type branding, companion object pattern, as const, escape hatches, type assertion, how do I narrow a type, how do I write a type predicate, how to create nominal types, how to prevent structural aliasing, make illegal states unrepresentable, illegal states, state machine types, entity lifecycle types, optional field anti-pattern, discriminated union state modeling, interface vs type alias, when to use interface vs type, enum best practices, typescript enum, const enum, readonly property, ReadonlyArray, lazy object initialization, barrel exports, when to use generics, generic naming conventions, no interface prefix. DO NOT USE when: runtime/schema validation at boundaries (parsing e

2026-07-264

typescript-zod

bsene/skills

Zod v4 best practices — schema design, error handling, transforms, coercion, branded types, and boundary validation. TRIGGER when: user mentions zod, zod validation, zod schema, zod v4, zod parse, zod transform, zod coerce, zod branded types, zod error handling, runtime validation, validate API response, schema composition, zod object, zod mini, zod infer, zod v3 to v4, migrate from zod v3, upgrade zod, zod breaking changes. DO NOT USE when: the question is pure compile-time typing with no runtime validation (discriminated unions, generics, narrowing, `as const`) → use `typescript-type-system`.

2026-07-264

git-hero-git-guru

bsene/skills

Expert Git assistant that answers questions about Git concepts, commands, workflows, and best practices — both in French and English. Use this skill whenever the user mentions Git, version control, commits, branches, merges, rebases, conflicts, stash, push/pull, remotes, history rewriting, or anything related to source code versioning. Also trigger when users say things like 'comment faire un rebase', 'I messed up my history', 'explain branching strategies', 'how do I undo a commit', 'what is the difference between merge and rebase', 'git tips', 'commit message best practices', or any git-related question — even phrased casually or in French. DO NOT USE when: choosing a commit-message emoji → use git-hero-gitmoji; designing/optimizing GitLab CI pipelines → use git-hero-gitlab-dag; non-Git version control (SVN, Mercurial, Perforce).

2026-07-264

git-hero

bsene/skills

Git best practices — commit discipline, branching/history hygiene, safety, and CI/CD pipelines. Routes to `git-guru` (expert Q&A), `gitmoji`, and `gitlab-dag` sub-skills. TRIGGER when: commits (Conventional Commits, atomic commits, commit message format, commit hygiene), history (branch naming, rebase vs merge, clean git history, interactive rebase, history management), safety (force push safety, recover lost commits, reflog, reset), CI/CD (GitLab CI, pipeline optimization, DAG, .gitlab-ci.yml), emoji (gitmoji, commit emoji, "quel emoji pour ce commit"), setup (git configuration, "bonnes pratiques git", "comment faire un rebase", "configure git properly"). DO NOT USE when: user needs a single one-shot git command answer — let Claude answer directly.

2026-07-264

name	git-hero-gitmoji
description	Selects and applies gitmoji emoji prefixes for Git commit messages, integrated with Conventional Commits format. Use when the user asks about gitmoji, wants an emoji for a commit message, asks 'which emoji for...', 'quel emoji pour...', mentions commit emoji conventions, says 'prefix my commit', 'gitmoji for', 'emoji commit', or wants to decorate commit messages with standardized emoji. DO NOT USE when: the user wants plain Conventional Commits with no emoji; general Git help → use git-hero-git-guru.
user-invocable	false

Gitmoji

Standardized emoji guide for commit messages. Reference: gitmoji.dev

Conventional Commits Integration

Gitmoji prefixes the Conventional Commits format — the CC structure stays intact:

<emoji> <type>(<scope>): <description>

Examples:

Change	Commit message
Add Google OAuth login	`✨ feat(auth): add OAuth2 login with Google`
Fix cart double-submit	`🐛 fix(cart): prevent double-submission on slow networks`
Upgrade React to v19	`⬆️ chore(deps): upgrade React to v19`

CC Type → Default Gitmoji

CC Type	Emoji	Code
`feat`	✨	`:sparkles:`
`fix`	🐛	`:bug:`
`docs`	📝	`:memo:`
`style`	🎨	`:art:`
`refactor`	♻️	`:recycle:`
`perf`	⚡️	`:zap:`
`test`	✅	`:white_check_mark:`
`chore`	🔧	`:wrench:`
`ci`	💚	`:green_heart:`
`build`	👷	`:construction_worker:`
`revert`	⏪️	`:rewind:`

Use the default when no more specific gitmoji applies. Override with a more precise emoji when the context warrants it (see below).

Selection Guide — Overriding Defaults

Fix variants

Situation	Emoji	Code
Regular bug fix	🐛	`:bug:`
Critical production hotfix	🚑️	`:ambulance:`
Simple non-critical fix	🩹	`:adhesive_bandage:`
Security or privacy fix	🔒️	`:lock:`
Typo fix	✏️	`:pencil2:`
Compiler / linter warning fix	🚨	`:rotating_light:`

Feat variants

Situation	Emoji	Code
New feature (default)	✨	`:sparkles:`
New project / initial commit	🎉	`:tada:`
UI / style changes	💄	`:lipstick:`
Animations / transitions	💫	`:dizzy:`
Business logic	👔	`:necktie:`

Chore variants

Situation	Emoji	Code
Configuration files	🔧	`:wrench:`
Dev scripts	🔨	`:hammer:`
Add dependency	➕	`:heavy_plus_sign:`
Remove dependency	➖	`:heavy_minus_sign:`
Upgrade dependency	⬆️	`:arrow_up:`
Downgrade dependency	⬇️	`:arrow_down:`
Pin dependency	📌	`:pushpin:`
.gitignore	🙈	`:see_no_evil:`

Removal variants

Situation	Emoji	Code
Remove code or files	🔥	`:fire:`
Remove dead code specifically	⚰️	`:coffin:`
Deprecate (mark for future cleanup)	🗑️	`:wastebasket:`

Common Confusions

:art: vs :recycle: — :art: is cosmetic (formatting, structure). :recycle: is behavioral (logic refactoring).
:fire: vs :coffin: — :fire: removes any code/files. :coffin: specifically targets dead/unreachable code.
:wrench: vs :hammer: — :wrench: is config files (tsconfig, eslint). :hammer: is dev scripts (Makefile, build scripts).
:white_check_mark: vs :test_tube: — :white_check_mark: for passing tests. :test_tube: for intentionally failing tests (TDD red phase).
:sparkles: vs :heavy_plus_sign: — :sparkles: adds a feature. :heavy_plus_sign: adds a dependency.

Top 20 Quick Reference

Emoji	Code	Description
✨	`:sparkles:`	New feature
🐛	`:bug:`	Bug fix
📝	`:memo:`	Documentation
♻️	`:recycle:`	Refactor
⚡️	`:zap:`	Performance
🎨	`:art:`	Code structure / format
🔥	`:fire:`	Remove code / files
✅	`:white_check_mark:`	Tests
🚀	`:rocket:`	Deploy
💄	`:lipstick:`	UI / style
🔧	`:wrench:`	Configuration
⬆️	`:arrow_up:`	Upgrade dependency
💚	`:green_heart:`	Fix CI
👷	`:construction_worker:`	CI build system
🚧	`:construction:`	Work in progress
🚑️	`:ambulance:`	Critical hotfix
🔒️	`:lock:`	Security fix
⏪️	`:rewind:`	Revert
🗃️	`:card_file_box:`	Database changes
🏷️	`:label:`	Types

Full Catalog

For the complete 73-emoji catalog grouped by category, see references/gitmoji-catalog.md.

Benchmark

Scenarios: .benchmarks/scenarios/gitmoji-001-security-and-optout.md, gitmoji-002-disambiguation.md · Run: 2026-06-26

Scenario	Model	Without	With	Delta
002 disambiguation	claude-opus-4-8	83%	100%	+17%
002 disambiguation	claude-sonnet-4-6	83%	100%	+17%
002 disambiguation	claude-haiku-4-5	67%	100%	+33%

PASS. The load-bearing lift is the override / Common-Confusions tables. On gitmoji-002 every baseline picked generic 🔥 :fire: for dead-code removal (should be ⚰️ :coffin:) and haiku also missed ➕ for a new dependency; the skill fixes both — haiku 67→100 (+33). gitmoji-001 (security override + no-emoji opt-out) was at ceiling (all models 100% with and without — no regression; the opt-out is honoured unaided), so value lives in the subtle picks. Gate per skill-optimizer/release-gates.md.