adr-log
Document Architecture Decisions with ADRs
Teams forget why major technical choices were made. This skill helps draft, review, and organize ADRs with clear context, alternatives, and consequences.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "adr-log" from https://skillstore.io/skills/doyajin174-adr-log.md and its manifest at https://skillstore.io/api/skills/doyajin174-adr-log/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "adr-log". We chose Next.js App Router for a new marketing and product site.
Expected outcome:
A complete ADR with accepted status, decision context, compared alternatives, expected benefits, tradeoffs, risks, and reference links.
Using "adr-log". Our team needs a decision history for database and authentication choices.
Expected outcome:
An ADR folder plan, numbering scheme, index outline, and checklist for consistent future records.
Using "adr-log". An older ADR chose MongoDB, but the product now requires stronger relational integrity.
Expected outcome:
A superseding ADR that explains the changed context, compares migration options, and records consequences for the team.
Security Audit
SafeThe static command findings are false positives from markdown code fences, inline filenames, and optional CLI examples. The hardcoded URLs are reference links, and the entropy heuristic reflects readable markdown with Korean text, not obfuscation. No prompt injection, data exfiltration intent, or hidden executable behavior was found.
Risk Factors
โ๏ธ External commands (25)
๐ Network access (5)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/doyajin174-adr-log/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/doyajin174-adr-log?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/doyajin174-adr-log?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/doyajin174-adr-log/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/doyajin174-adr-log.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
Doyajin174. (2026). adr-log security audit report (audit version 8) [Author version 1.0]. Skillstore. https://skillstore.io/skills/doyajin174-adr-log/audits/8BibTeX citation
@techreport{doyajin174-doyajin174-adr-log-2026,
author = {Doyajin174},
title = {adr-log security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/doyajin174-adr-log/audits/8},
note = {Author version 1.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "adr-log security audit report (audit version 8)"
version: "1.0"
type: report
authors:
- name: "Doyajin174"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/doyajin174-adr-log/audits/8"
identifiers:
- type: other
value: "skillstore:doyajin174-adr-log:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Record Framework Decisions
Capture why a team selected a frontend, backend, database, or library option over alternatives.
Onboard New Engineers
Create a readable decision history that explains past tradeoffs for new team members.
Review High Impact Changes
Use ADRs during pull requests to document infrastructure, security, or platform decisions.
Try These Prompts
Use adr-log to draft an ADR for choosing PostgreSQL. Include context, alternatives, decision, consequences, risks, and references.
Review my draft ADR for clarity, missing alternatives, weak rationale, and unclear consequences. Suggest specific edits.
Create an ADR index for these decisions with numbers, titles, statuses, dates, and short summaries.
Analyze these related ADRs and draft a new ADR that supersedes the outdated decision. Explain migration impact and remaining risks.
Best Practices
- Write an ADR soon after team alignment, while the rationale is still clear.
- Document serious alternatives and tradeoffs, not only the final choice.
- Use a new ADR to supersede old decisions instead of silently rewriting history.
Avoid
- Do not use ADRs for small implementation details with no lasting impact.
- Do not write only the chosen option without context or rejected alternatives.
- Do not keep decisions only in chat, meetings, or pull request comments.
Frequently Asked Questions
What is an ADR?
When should I use this skill?
Can it create ADR files for me?
Does it require adr-tools?
Can I use it with Claude Code or Codex?
How should old decisions be changed?
Developer Details
Author
Doyajin174License
MIT
Author version
v1.0
Skillstore revision
r1
Version notice
The author-declared version is not valid SemVer.
Ref
72d5025b022c77f7a51bdf5c1637c689c80e89d1
Maintenance freshness
7/18/2026
Usage
4 downloads ยท 233 views
File structure
๐ audit_output.json
๐ SKILL.md