commit-style

Crafts and generates professional conventional commit messages following Angular/Conventional Commits format. Use when committing changes, writing git commit messages, or when user mentions commit message.

Ir a la instalación Revisar archivos

Repositorio: Tibsfox/gsd-skill-creator
Última actividad en el origen: 7 de julio de 2026 a las 04:19
Idioma detectado de SKILL.md: inglés
Estrellas: 70
Forks: 10

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con un asistente de IA

Copia este prompt en el asistente de IA que estés usando.

Follow https://skillsmp.com/skill-install/prompt.md to install only the Agent Skill at https://github.com/Tibsfox/gsd-skill-creator/tree/main/project-claude/skills/commit-style.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/Tibsfox/gsd-skill-creator --skill commit-style

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

name: commit-style
description: Crafts and generates professional conventional commit messages following Angular/Conventional Commits format. Use when committing changes, writing git commit messages, or when user mentions commit message.
format: 2025-10-02T00:00:00.000Z
version: 1.0.0
status: ACTIVE
updated: 2026-04-15T00:00:00.000Z
triggers: ["committing changes, writing git commit messages, or when user mentions commit message"]

# Commit Style — Conventional Commits Generates commit messages following the Conventional Commits / Angular convention for clear, consistent version history. ## Format ``` <type>(<scope>): <subject> [optional body] [optional footer] ``` ## Types | Type | Use | |------|-----| | `feat` | New feature | | `fix` | Bug fix | | `docs` | Documentation only changes | | `style` | Formatting, whitespace, no logic change | | `refactor` | Neither fix nor feature | | `perf` | Performance improvement | | `test` | Adding or updating tests | | `build` | Build system or external dependencies | | `ci` | CI/CD configuration changes | | `chore` | Other maintenance tasks | | `revert` | Reverting a previous commit | ## Rules - **Subject:** ≤72 chars (50 preferred), lowercase, imperative mood, no trailing period. - **Imperative test:** "If applied, this commit will _[subject]_". - **Scope:** Specific module/component in lowercase — e.g. `feat(auth)`, `fix(api)`, `docs(readme)`, `refactor(core)`. - **Body:** Optional. Explain WHY/WHAT, not HOW. Wrap at 72 chars. Blank line between subject and body. - **Footer:** Optional. `BREAKING CHANGE: …`, `Closes #N`, `Co-Authored-By: …` (HUMAN co-authors only — `Co-Authored-By: Claude …` trailers are hard-blocked by `.claude/hooks/validate-commit.cjs`, v1.49.621 policy). ## Atomic Commits One logical change per commit. Split unrelated changes into separate commits — this makes surgical rollback and `git bisect` possible. ## Examples Simple feature: ``` feat(auth): add password reset functionality ``` Bug fix with issue reference: ``` fix(api): handle null response from user endpoint The /users/:id endpoint could return null for deleted users, causing a crash in the profile component. Closes #456 ``` Breaking change: ``` feat(api): change authentication to JWT Migrate from session-based auth to JWT tokens for better scalability and stateless operation. BREAKING CHANGE: All API clients must now include JWT token in Authorization header. Session cookies no longer accepted. ``` Documentation update: ``` docs(readme): update installation instructions Add troubleshooting section for common npm issues and clarify Node.js version requirements. ``` ## Anti-Patterns - Vague subjects: "fix bug", "update stuff" - Past/present tense: "added", "adds" — use the imperative "add" - Multiple changes in one commit: "add login and fix navbar" - Implementation trivia: "change line 47" - Emotional language: "finally fixed!!!"

Ver en GitHub

Volver a la búsqueda Volver a la instalación

goal-ambiguity-gate

Use the moment a request is underspecified and you are about to act on an ASSUMED goal. Enumerate the candidate goals the request could mean, project the action or artifact each one implies, and check whether they diverge: if two or more plausible goals lead to materially different actions or artifacts, ask exactly ONE targeted clarifying question; otherwise proceed on the most-likely goal and state the assumption in one line. Clarification is an evidence-producing action, not a delay — but one question, never an interrogation. Distinct from gsd-spec-phase (GSD-phase-bound, emits a heavy SPEC.md) and intent-router (fetch strategy, not goal disambiguation). Backed by agent goal-state inference (arxiv 2606.16813v1). Triggers on acting under an assumed goal when the request admits more than one materially different reading.

2026-07-19

memory-hubness-gate

Use at write time to vector/embedding memory — Grove content-addressed insertion, chroma/pgvector upserts, memory-consolidation promoting session traces to MEMORY.md, or embedding externally-ingested content. Scores each candidate record against a fixed panel of sentinel queries and quarantines any record that would become the nearest neighbor of too many unrelated queries — a hub — whether from adversarial poisoning or accidental over-generality. This is the memory-record-side sibling of skill-injection-guardian (file-side) and the write-side complement of memory-use-warrant (read-side). Quarantine, never silently drop; a human reviews. Backed by the admission-time hubness gate (arxiv 2606.19692v1). Triggers on inserting into vector memory, consolidating memory, and embedding stranger content.

2026-07-19

memory-use-warrant

Run this appropriateness check the moment you are about to integrate a retrieved long-term memory — a Grove content-addressed hit, a chroma/pgvector neighbour, a memory-consolidation digest, or a MEMORY.md line — into a response, especially anything touching private origins, Fox Companies IP, credentials, or Center Camp / consent-governed content. It answers a question intent-router never asks: not WHAT to fetch or HOW, but WHETHER a correctly-retrieved item should reach output. Relevance is not appropriateness — a perfect similarity match can still be a boundary violation. Default is FAIL-CLOSED: if in-context authorization is uncertain, the memory may inform behaviour but must not be surfaced. Backed by RBI-Eval (arxiv 2606.06055v1). Triggers on surfacing recalled sensitive memory into a response.

2026-07-19

Ver todos los de este repositorio

commit-style

Datos de origen

Opciones de instalación

Instalar con un asistente de IA

Revisa los archivos de origen

Más de este repositorio

Instalar con un asistente de IA

Más de este repositorio