1K skills · sorted by relevance
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
恒常的な設計決定を ADR として記録する（退役する機能仕様から ADR 昇格の要否を判定するモードを併せ持つ）。定常フローの必須ステップではなく、必要時に呼ぶ。Triggers on: '/create-adr', 'ADRを書いて', '設計判断を記録', 'ADR昇格を判定'
The English summary is being prepared. Showing the original description.
Record software design decisions as numbered Markdown files, with context, rejected alternatives, benefits, drawbacks, and risks. Maintain an index and consult existing ADRs—architecture decision records—to explain why a framework, database, or design approach was chosen.
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.
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).
The English summary is being prepared. Showing the original description.
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.
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.
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.
The English summary is being prepared. Showing the original description.
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.
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.