本文へ移動
cccskills
無料GitHub で公開

adr

Create and manage Architecture Decision Records (ADRs). Use when making architectural changes (refactoring, API versioning, new domain layers, schema changes), when reviewing recent commits for documentation needs, or when the user mentions ADR, architecture decisions, or documenting technical decisions.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md2.7 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Architecture Decision Records

Create and manage ADRs in packages/web/src/content/docs/docs/contributing/adrs/ to document significant architectural decisions. ADRs are published on the docs site under Contributing.

Instructions

When to Create an ADR

Suggest creating an ADR when detecting:

  • Commits containing: refactor, architecture, migrate, introduce, domain layer, api version
  • New files in: domain/, api/, services/, models/
  • Schema changes: prisma/schema.prisma modified
  • Config changes: tsconfig.json, eslint.config.js significantly changed

Skip ADR suggestion for:

  • Commits containing only: fix, chore, docs, test, style
  • Changes only in: tests/, *.test.ts, *.spec.ts
  • Single file changes under 50 lines

Creating an ADR

  1. Find the next ADR number by listing packages/web/src/content/docs/docs/contributing/adrs/
  2. Check recent plan files in ~/.claude/plans/ for context
  3. Analyze recent commits: git log --since="7 days ago" --oneline
  4. Extract Context, Decision, and Rationale from plans/commits
  5. Create the ADR file using the template below in packages/web/src/content/docs/docs/contributing/adrs/
  6. Update the index page at packages/web/src/content/docs/docs/contributing/adrs/index.md

Listing ADRs

List existing ADRs: ls -1 packages/web/src/content/docs/docs/contributing/adrs/*.md | grep -v index

Template

Use Michael Nygard format in packages/web/src/content/docs/docs/contributing/adrs/NNN-kebab-case-title.md:

---
title: 'ADR-XXX: Title'
description: One-sentence summary of the decision.
---

**Status:** Accepted
**Date:** YYYY-MM-DD
**Authors:** [Names]

## Context

[What is the issue we're solving? What forces are at play?]

## Decision

[What is the change we're making?]

## Rationale

[Why is this the right choice?]

## Consequences

### Positive

- [Benefit 1]

### Negative

- [Tradeoff 1]

## Related Commits

- `hash` - commit message

Examples

User asks: "Document the recent API versioning changes" Action: Create ADR covering the v1 prefix, Zod validation, and thin client decisions

After refactoring: When Claude completes a significant refactor, proactively suggest documenting the decision

Reviewing work: When asked to review recent architectural changes, check if ADRs exist and suggest creating them if missing

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

doc-sync

無料

Detect documentation and architecture-model drift by comparing source-of-truth code (CLI commands, flags, env vars, GH Action inputs/outputs, package structure, pipeline stages, providers, adapters, platforms) against web docs, README, and LikeC4 architecture model (.c4 files). Use when files that define the user-facing interface or internal structure change, when the user asks to check docs, or when mentioning doc drift, architecture drift, stale docs, or documentation sync.

日本語の概要は準備中です。原文の説明を表示しています。

erode-app/erode522026年10月8日 更新

Enforce the project's documentation voice when writing or reviewing public-facing content. Triggers on edits to doc files (packages/web/src/content/docs/**/*.md) and README.md. Catches LLM prose patterns, marketing language, and messaging drift.

日本語の概要は準備中です。原文の説明を表示しています。

erode-app/erode522026年10月8日 更新

Use this skill whenever code changes introduce new imports, API calls, database connections, message queues, or service-to-service communication. Also use before any commit or push. Catches undeclared dependencies and architecture violations using Erode.

日本語の概要は準備中です。原文の説明を表示しています。

erode-app/erode522026年10月8日 更新

Generate product pitch videos for the Erode project from screenshots. Use this skill whenever the user wants to create, update, or regenerate the product demo video, landing page animation, or pitch clip for erode.dev or the GitHub repo. Also trigger when the user mentions "product video", "demo video", "pitch video", "update the video", "regenerate video", or "landing page animation" in the context of Erode.

日本語の概要は準備中です。原文の説明を表示しています。

erode-app/erode522026年10月8日 更新

Conventional commits with project conventions. Use when the user asks to commit, make a commit, or wants to follow the project's git commit standard.

日本語の概要は準備中です。原文の説明を表示しています。

erode-app/erode522026年10月8日 更新

Sync the local LikeC4 syntax guide with the upstream LikeC4 skills repository (github.com/likec4/likec4/tree/main/skills/likec4-dsl). Use when the user asks to update, sync, or check the LikeC4 syntax guide, when upstream LikeC4 DSL changes are suspected, or when mentioning likec4 syntax sync, DSL drift, or syntax guide update.

日本語の概要は準備中です。原文の説明を表示しています。

erode-app/erode522026年10月8日 更新

erode-app のスキルをすべて見る

このスキルの問題を報告する