원클릭으로 Manus에서 모든 스킬 실행

git-hero

스타4

포크0

업데이트2026년 7월 9일 23:51

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.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

bsene

bsene/skills

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Git Hero

Comprehensive Git mastery — best practices, expert Q&A, gitmoji, and CI/CD pipelines.

Route to Sub-skills

Route immediately on keyword match. Answer inline only for quick factual git questions not covered by a sub-skill.

-> Git Q&A — route when: user asks about concepts, commands, workflows, internals, troubleshooting, conflicts, stash, rebase, reflog, or anything "how do I do X in git?" → git-guru/ sub-skill -> Gitmoji — route when: user asks about commit emoji, gitmoji prefix, "which emoji for this commit?", or emoji commit conventions → gitmoji/ sub-skill -> GitLab CI/CD — route when: user mentions GitLab pipelines, DAG, needs:, parallel matrix, .gitlab-ci.yml, or pipeline optimization → gitlab-dag/ sub-skill

Commit Discipline

Format

Every commit message follows Conventional Commits, optionally prefixed with gitmoji:

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

Rules:

One-liner only -- no body, no footer, no blank lines
Imperative mood -- "add feature" not "added feature" or "adds feature"
Lowercase description -- no capital after the colon
No trailing period
Scope is optional but recommended for multi-module repos

Examples:

feat(auth): add OAuth2 login with Google
fix(cart): prevent double-submission on slow networks
refactor: extract validation into shared module

Atomic Commits

One logical change per commit. Each commit should:

Compile and pass tests on its own
Be revertable without side effects
Have a message that fully describes the change

Smell test: if the message needs "and", split the commit.

Read On Demand

Read When	File
Configuring git (aliases, GPG signing, push safety, force push, reflog, modern syntax, rerere)	Config Recipes
Choosing a workflow, merge vs rebase, branch naming conventions, branch lifecycle	Workflow Decisions

이 저장소의 다른 Skills

같은 저장소

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).

name	git-hero
description	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.
user-invocable	false

Git Hero

Comprehensive Git mastery — best practices, expert Q&A, gitmoji, and CI/CD pipelines.

Route to Sub-skills

Route immediately on keyword match. Answer inline only for quick factual git questions not covered by a sub-skill.

Commit Discipline

Format

Every commit message follows Conventional Commits, optionally prefixed with gitmoji:

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

Rules:

One-liner only -- no body, no footer, no blank lines
Imperative mood -- "add feature" not "added feature" or "adds feature"
Lowercase description -- no capital after the colon
No trailing period
Scope is optional but recommended for multi-module repos

Examples:

feat(auth): add OAuth2 login with Google
fix(cart): prevent double-submission on slow networks
refactor: extract validation into shared module

Atomic Commits

One logical change per commit. Each commit should:

Compile and pass tests on its own
Be revertable without side effects
Have a message that fully describes the change

Smell test: if the message needs "and", split the commit.

Read On Demand

Read When	File
Configuring git (aliases, GPG signing, push safety, force push, reflog, modern syntax, rerere)	Config Recipes
Choosing a workflow, merge vs rebase, branch naming conventions, branch lifecycle	Workflow Decisions