'adr' 검색 결과

Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Rebuild the index after deleting an ADR file
• Remove stale relationships after editing an ADR
• Reconcile the ADR index on a schedule

Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Index ADRs imported from another project
• Refresh a graph that differs from files on disk
• Set up ADR tracking in an existing codebase

Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking ADR integrity after import
• Blocking CI when ADR issues are found
• Reviewing ADR data before a release

Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check a pull request before merging
• Review major code changes against agreed design decisions
• Find references to superseded ADRs

Automate Adrapid operations through Rube MCP, a connection for agent tools. The skill discovers available actions and their required inputs, checks the Adrapid connection, and executes tasks using the current tool definitions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find available tools for an Adrapid task
• Check and set up an Adrapid connection
• Run Adrapid tasks through an agent

Automate Adrapid operations through Rube MCP, a connection for agent tools. The skill discovers available actions and their required inputs, checks the Adrapid connection, and executes tasks using the current tool definitions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find available tools for an Adrapid task
• Check and set up an Adrapid connection
• Run Adrapid tasks through an agent

Review and rewrite architecture decision records, documents that explain design choices, from a newcomer’s perspective. Identify missing context, buried decisions, and temporary details, then reorganize each document so future readers can follow the reasoning.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing design decisions from a new team member’s perspective
• Making an ADR’s decision and reasoning easier to follow
• Removing temporary project context from long-lived records

Automate Codereadr tasks using Rube MCP and Composio. The skill guides tool discovery, connection checks, and execution based on current input requirements, with instructions for keeping related steps within the same session.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Looking up available Codereadr tools
• Checking the Codereadr connection before a task
• Executing operations using current input requirements

Automate Codereadr tasks using Rube MCP and Composio. The skill guides tool discovery, connection checks, and execution based on current input requirements, with instructions for keeping related steps within the same session.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Looking up available Codereadr tools
• Checking the Codereadr connection before a task
• Executing operations using current input requirements

Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Record the reasoning behind adopting a technology
• Start an ADR for an API or data model change
• Document an infrastructure decision

Write architecture decision records, short documents explaining a software design choice, its context, and its consequences. It helps decide what deserves a record, select a template, organize files, and link replacement decisions to earlier records.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Record why a database or library was chosen
• Set up a directory for decision records
• Choose an ADR template that fits the decision

Document major technical choices as Architecture Decision Records, or ADRs. Capture the context, alternatives, reasons, and consequences, then organize related records and track whether decisions are proposed, accepted, retired, or replaced.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Recording reasons for choosing a framework or database
• Comparing design options and their trade-offs
• Sharing past decisions with new team members

Create ADRs, short records of architectural decisions, that explain what was chosen, why, and with what trade-offs. Choose among three formats and organize dates, status, numbering, and related links for future team members.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Recording why a database was chosen
• Preserving the rationale for a framework choice
• Documenting an authentication approach

Compare a Chinese company's US depositary receipts, Hong Kong shares, and mainland shares after adjusting for exchange rates and share ratios. Analyze pricing gaps, valuation differences, and delisting risks to support research into its different listings.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Compare A-share and H-share pricing gaps
• Measure ADR premiums against Hong Kong shares
• Review US delisting risks and Hong Kong listing alternatives

Document a technical decision in an architecture decision record, or ADR. Capture its context, alternatives, and consequences, assign a record number, and distinguish a proposed decision from an accepted one so dependent work reflects its actual status.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Recording the reasons behind a technical choice
• Documenting alternatives and consequences of a design decision
• Creating numbered records alongside existing architecture decisions

恒常的な設計決定を ADR として記録する（退役する機能仕様から ADR 昇格の要否を判定するモードを併せ持つ）。定常フローの必須ステップではなく、必要時に呼ぶ。Triggers on: '/create-adr', 'ADRを書いて', '設計判断を記録', 'ADR昇格を判定'

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

기술이나 설계를 선택한 이유를 배경, 대안, 영향과 함께 Markdown으로 기록합니다. 일련번호와 색인으로 정리하고 기존 기록에서 과거 판단의 근거도 찾습니다.

• 프레임워크나 데이터베이스 선택 이유 기록
• 설계 대안과 장단점 정리
• 과거 기술 결정의 근거 확인

Maintain a collection of architecture decision record templates, examples, translations, and tool links. It explains which files to update for each contribution and how to review pull requests for completeness, consistent formatting, and relevant content.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add an ADR template to the collection
• Add a worked decision record example
• Update links to ADR tools and pull request checks

Use when writing or formatting an ADR document using the MADR template, applying Definition of Done (E.C.A.D.R.) criteria, or verifying ADR completeness. Triggers on "write the ADR", "format as MADR", "check ADR quality", "mark gaps in ADR". Also triggers when a decision has been extracted and needs to become a document. Does NOT extract decisions from conversations (use adr-decision-extraction) or orchestrate the full extract-confirm-write workflow (use write-adr).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write and maintain Architecture Decision Records (ADRs), documents explaining important technical choices. Capture the context, options, decision, and consequences, then organize records and track their status so teams can revisit the reasoning.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Record the reasons for choosing a framework or database
• Document design options and their trade-offs
• Explain past technical decisions to new team members

Turn accepted architecture decisions, project preferences, and engine references into a practical rules document. Organize required patterns, forbidden approaches, and performance limits by architectural layer, with a source attached to each rule.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Consolidating implementation rules from accepted decisions
• Updating rules after architecture decisions change
• Reviewing naming conventions and performance limits

Create, review, and manage Architecture Decision Records (ADRs) with auto-numbering, template detection, quality review, and index maintenance. Use when user mentions "ADR", "architecture decision", "document this decision", "create ADR", "review ADR", editing ADR files (docs/adr/, doc/adr/, .adr/), or discussing architectural choices and tradeoffs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Make system architecture decisions by clarifying requirements and constraints, comparing benefits and drawbacks, and considering simpler alternatives. Record the reasoning in ADRs, architecture decision records, so significant choices and their rationale are documented.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Clarifying requirements before system design
• Comparing architecture patterns
• Documenting decisions and rationale in ADRs

Trace changes in a game design document to related architecture decision records, which explain technical choices. Compare their assumptions with the revised design, report which decisions need review, and guide updates to decisions and requirement links.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking architecture impact after changing game design
• Finding technical decisions based on outdated requirements
• Choosing whether to keep, revise, or replace a decision