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 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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

모든 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일