alexbruno/dev-skills

decision-records

Document significant technical and architectural decisions as lightweight Architecture Decision Records (ADRs).

Ver código-fonte

Como usar

  1. Copie o comando e verifique o pacote antes de instalar no seu ambiente de agente.
  2. Consulte no original as ferramentas, credenciais e ambientes necessários.
  3. Descreva os dados de entrada e a entrega esperada; confira a saída com as fontes.
npx skills add https://github.com/alexbruno/dev-skills --skill decision-records

Antes de começar

  • A instalação não inclui assinatura de modelo, franquia API ou acesso aos seus arquivos.
  • Estrelas e instalações indicam atividade, não um teste independente de qualidade ou segurança.
Documento original do Skill

Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.

Decision Records (ADRs)

Capture why important technical decisions were made—along with alternatives considered and trade-offs accepted—in concise, immutable Markdown records.

When to Create an ADR

Create an ADR when a change involves:

  • A hard-to-reverse architectural or data-model choice.
  • A cross-cutting trade-off affecting multiple modules, services, or teams.
  • Adding or replacing a core dependency, protocol, storage engine, or integration pattern.

Skip ADRs for routine implementation details, local refactorings, or easily reversible choices—those belong in workflow/PLAN.md or code comments.

Storage & Naming

  • Store records in docs/decisions/ (or docs/adr/ if the repository already uses that convention).
  • Name files sequentially with a lowercase hyphenated slug:

docs/decisions/0001-short-decision-title.md

  • Start from the template in ADR.md.

Rules

  1. Link with `workflow/`: Reference the ADR from workflow/PLAN.md (and workflow/SPEC.md if applicable) so design context stays connected.
  2. Keep it concise: Focus on context, decision, alternatives rejected, and consequences—avoid turning an ADR into a tutorial or full specification.
  3. Immutable history: Once accepted, do not rewrite an old ADR's intent; if a decision changes later, create a new ADR that marks the previous one as Superseded by <ADR-XXXX>.
do mesmo repositório

Mais Skills

Todos os Skills
alexbruno
Comunidade

architect-worker

Role-based multi-agent software engineering pattern separating high-level architecture, specification, planning, and code review (Architect) from focused code implementation and verification (Worker). Use this skill whenever assigned the Architect or Worker role (in any language), or when coordinating work between planning/review agents and implementation agents via workflow/.

Instalações / 1h
1
GitHub Stars
0
Atualizado
13 de nov.
alexbruno
Comunidade

changelog-management

Maintain and update a standardized root CHANGELOG.md following Keep a Changelog and Semantic Versioning. Use this skill to initialize or update changelog entries, categorize changes, prepare release cuts, and proactively prompt the user when notable changes warrant updating the changelog.

Instalações / 1h
1
GitHub Stars
0
Atualizado
13 de nov.
alexbruno
Comunidade

code-review

Perform structured, multi-dimensional code reviews aligned with the spec-driven-workflow (workflow/SPEC.md, workflow/PLAN.md, workflow/REVIEW.md). Use this skill after implementing a feature or bug fix, before merging a PR, or when reviewing changes written by another agent or human.

Instalações / 1h
1
GitHub Stars
0
Atualizado
13 de nov.
alexbruno
Comunidade

code-simplification

Simplify code for human readability, clarity, and directness without changing behavior. Use this skill after implementing a feature, during refactoring, or when addressing code review feedback—especially when code feels over-engineered, deeply nested, or takes unnecessary detours to do simple things.

Instalações / 1h
1
GitHub Stars
0
Atualizado
13 de nov.