Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

speckit-git-commit

Estrellas5

Forks4

Actualizado14 de mayo de 2026, 19:22

Compose Conventional Commits messages and stage the right files for a pickup-points-modal change, respecting CHANGELOG and the constitution's backward-compat principle.

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

vtex

vtex/pickup-points-modal

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

SKILL.md

readonly

name	speckit-git-commit
description	Compose Conventional Commits messages and stage the right files for a pickup-points-modal change, respecting CHANGELOG and the constitution's backward-compat principle.
type	skill

speckit-git-commit

Compose commit messages in the repo's Conventional Commits style.

Format

<type>(<scope>): <subject>

<body>

<footer>

Accepted types

Type	When to use
`feat`	User-visible feature
`fix`	Bug fix
`chore`	Tooling/deps without functional change
`docs`	Documentation change (README, CHANGELOG, AGENTS)
`refactor`	Refactor without functional change
`test`	Tests only
`perf`	Performance improvement

Suggested scopes

modal — PickupPointsModal.js, ModalState.js
map — Google Maps components
i18n — messages/
fetchers — react/fetchers/
tooling — config files

Rules tied to the constitution

Breaking change in PickupPointsModal props/events:
- Add BREAKING CHANGE: in the footer.
- Major bump in manifest.json (ask first).
- CHANGELOG entry.
i18n change: scope i18n and list the locales touched in the body.

Staging

Always stage by specific path (git add react/components/X.js), never git add -A or git add . — those can pull in .env* or build artifacts.
Confirm with git status before committing.

Don't

--no-verify to skip hooks.
Subject in uppercase.
Subject longer than 72 chars.

Más de este repositorio

mismo repositorio

implementing

vtex/pickup-points-modal

Implement an approved spec end-to-end in the pickup-points-modal repo — branch, code, tests, lint, typecheck, build, commit, and open a PR following Conventional Commits and the project constitution.

2026-05-145

specification

vtex/pickup-points-modal

Generate an SDD (Spec Driven Development) document for a new feature in the pickup-points-modal, covering Business Context, Architectural Decisions, and Technical Contract before any code is written.

2026-05-145

speckit-analyze

vtex/pickup-points-modal

Audit consistency between spec.md, plan.md, tasks.md, and the actual code in the pickup-points-modal — flagging drift, missing tasks, or out-of-spec changes before PR review.

2026-05-145

speckit-checklist

vtex/pickup-points-modal

Generate a per-feature validation checklist (pre-merge gates, manual QA steps, rollback plan) for a pickup-points-modal feature, tailored to the spec and constitution principles.

2026-05-145

speckit-clarify

vtex/pickup-points-modal

Interactively clarify ambiguous requirements in a spec.md before planning — generates targeted questions for the requester to resolve TBDs in the pickup-points-modal feature spec.

2026-05-145

speckit-constitution

vtex/pickup-points-modal

Create or amend the project constitution in .specify/memory/constitution.md, capturing binding principles, governance, and ratification metadata for the pickup-points-modal.

2026-05-145

name	speckit-git-commit
description	Compose Conventional Commits messages and stage the right files for a pickup-points-modal change, respecting CHANGELOG and the constitution's backward-compat principle.
type	skill

speckit-git-commit

Compose commit messages in the repo's Conventional Commits style.

Format

<type>(<scope>): <subject>

<body>

<footer>

Accepted types

Type	When to use
`feat`	User-visible feature
`fix`	Bug fix
`chore`	Tooling/deps without functional change
`docs`	Documentation change (README, CHANGELOG, AGENTS)
`refactor`	Refactor without functional change
`test`	Tests only
`perf`	Performance improvement

Suggested scopes

modal — PickupPointsModal.js, ModalState.js
map — Google Maps components
i18n — messages/
fetchers — react/fetchers/
tooling — config files

Rules tied to the constitution

Breaking change in PickupPointsModal props/events:
- Add BREAKING CHANGE: in the footer.
- Major bump in manifest.json (ask first).
- CHANGELOG entry.
i18n change: scope i18n and list the locales touched in the body.

Staging

Always stage by specific path (git add react/components/X.js), never git add -A or git add . — those can pull in .env* or build artifacts.
Confirm with git status before committing.

Don't

--no-verify to skip hooks.
Subject in uppercase.
Subject longer than 72 chars.