commit — community commit, oxc-react-compiler, community, ide skills

v1.0
GitHub

Acerca de este Skill

Perfecto para agentes de desarrollo que necesitan un formato de mensaje de confirmación de Git estandarizado. Conventional commit message formatting. Use when creating git commits to ensure messages follow the projects conventional commit style with proper type, scope, and description.

SarthakMishra SarthakMishra
[0]
[0]
Updated: 3/13/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 9/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Quality floor passed for review
Review Score
9/11
Quality Score
62
Canonical Locale
en
Detected Body Locale
en

Perfecto para agentes de desarrollo que necesitan un formato de mensaje de confirmación de Git estandarizado. Conventional commit message formatting. Use when creating git commits to ensure messages follow the projects conventional commit style with proper type, scope, and description.

¿Por qué usar esta habilidad?

Habilita a los agentes a aplicar un formato de mensaje de confirmación convencional utilizando tipos, ámbitos y descripciones específicos, lo que garantiza la consistencia y la claridad en los commits de Git con el tipo, el ámbito y la descripción adecuados, utilizando protocolos como Git y estándares de formato como Conventional Commits.

Mejor para

Perfecto para agentes de desarrollo que necesitan un formato de mensaje de confirmación de Git estandarizado.

↓ Casos de uso accionables for commit

Establecer un estándar para los mensajes de confirmación de proyectos de equipo
Automatizar la validación de mensajes de confirmación para tuberías de CI/CD
Generar mensajes de confirmación con el tipo, el ámbito y la descripción adecuados

! Seguridad y limitaciones

  • Requiere el sistema de control de versiones Git
  • Limitado al formato Conventional Commits

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is commit?

Perfecto para agentes de desarrollo que necesitan un formato de mensaje de confirmación de Git estandarizado. Conventional commit message formatting. Use when creating git commits to ensure messages follow the projects conventional commit style with proper type, scope, and description.

How do I install commit?

Run the command: npx killer-skills add SarthakMishra/oxc-react-compiler/commit. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for commit?

Key use cases include: Establecer un estándar para los mensajes de confirmación de proyectos de equipo, Automatizar la validación de mensajes de confirmación para tuberías de CI/CD, Generar mensajes de confirmación con el tipo, el ámbito y la descripción adecuados.

Which IDEs are compatible with commit?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for commit?

Requiere el sistema de control de versiones Git. Limitado al formato Conventional Commits.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add SarthakMishra/oxc-react-compiler/commit. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use commit immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

commit

Install commit, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Conventional Commits

Format

<type>(<scope>): <description>
                                        ← blank line
<body>
  • type: required, lowercase
  • scope: optional, in parentheses, lowercase
  • description: required, lowercase start, imperative mood, no period
  • body: optional, separated by blank line, free-form with bullet lists

Types

TypeWhen to use
featNew compiler pass, HIR type, lint rule, or feature
fixBug fix
choreTooling, config, deps, no production code change
docsDocumentation only
refactorCode change that neither fixes a bug nor adds a feature
depsDependency additions or updates
testAdding or updating tests
ciCI/CD pipeline changes
perfPerformance improvement
styleFormatting, whitespace (no logic change)

Scope

Derive from the primary area of change:

  • HIR: hir, build-hir, environment, globals, object-shape
  • SSA: ssa
  • Optimization: optimization, const-prop, dce, inline-iife
  • Inference: inference, infer-types, mutation-analysis, aliasing
  • Reactive Scopes: reactive-scopes, scope-inference, scope-alignment, codegen
  • Validation: validation, hooks, refs, effects
  • Pipeline: pipeline, program, options
  • Lint: lint, lint-rules
  • NAPI/Plugin: napi, vite-plugin
  • Utils: disjoint-set, utils
  • Omit scope for broad cross-cutting changes

Rules

  1. Use imperative mood: "add feature" not "added feature" or "adds feature"
  2. Keep the first line under 72 characters
  3. Start description lowercase
  4. No trailing period
  5. One commit per logical change — don't mix unrelated changes

Examples

One-liners (small, focused changes)

feat(hir): add InstructionValue enum with 40 variants
fix(ssa): handle redundant phi elimination for loop headers
chore(deps): update oxc crates to 0.50
feat(validation): implement validate_hooks_usage pass

With body (multi-file or multi-step changes)

feat(inference): implement infer_mutation_aliasing_effects pass

- Build abstract heap model with pointer graph and ValueKind per value
- Fixpoint iteration to propagate effects through aliases
- Compute candidate effects based on instruction kind and operand types
- Record final AliasingEffect annotations on each instruction

feat(reactive-scopes): implement scope inference and alignment

- DisjointSet-based scope grouping in infer_reactive_scope_variables
- Align scopes to block boundaries
- Merge overlapping scopes with shared reactive operands
- Build reactive scope terminals for codegen

feat(build-hir): implement OXC AST to HIR lowering

- Walk oxc_ast Statement/Expression nodes
- Flatten nested expressions into temporaries with Places
- Convert control flow to explicit BasicBlock edges
- Handle JSX, hooks, destructuring, and closures

Body style guidelines

  • Use bullet lists (-) for discrete changes
  • Use prose paragraphs for narrative summaries of larger features
  • Group related bullets under subheadings when mixing concerns (e.g. "Fixes:")
  • Keep body lines under 72 characters

Habilidades relacionadas

Looking for an alternative to commit or another community skill for your workflow? Explore these related open-source skills.

Ver todo

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
Inteligencia Artificial

widget-generator

Logo of f
f

Generar complementos de widgets personalizables para el sistema de feeds de prompts.chat

★ 149.6k
⑂ 0
Inteligencia Artificial

flags

Logo of vercel
vercel

El Marco de React

★ 138.4k
⑂ 0
Navegador

pr-review

Logo of pytorch
pytorch

Tensores y redes neuronales dinámicas en Python con fuerte aceleración de GPU

★ 98.6k
⑂ 0
Desarrollador