alexbruno/dev-skills

decision-records

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

查看源码

使用方法

  1. 复制安装命令,在自己的智能体环境安装前先检查源码包。
  2. 从原始文档核对所需工具、凭据和支持的宿主。
  3. 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/alexbruno/dev-skills --skill decision-records

开始前需了解

  • 安装不包含模型订阅、API 额度或访问文件的权限。
  • 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
仓库原始内容

按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。

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>.
来自同一仓库

更多 Skills

全部 Skills
alexbruno
社区

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

1小时安装量
1
GitHub Stars
0
最近更新
11月13日
alexbruno
社区

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.

1小时安装量
1
GitHub Stars
0
最近更新
11月13日
alexbruno
社区

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.

1小时安装量
1
GitHub Stars
0
最近更新
11月13日
alexbruno
社区

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.

1小时安装量
1
GitHub Stars
0
最近更新
11月13日