skills.rest
archyl-com
archyl-comOFFICIAL
Explore all skills by this author →
Website𝕏@archyl_comGitHub

archyl-changelog

Aggregate change history, ADRs, releases, and drift into a structured markdown changelog.

1|Updated Mar 28, 2026
Search Tags:#changelog#architecture#adr#diff#drift#releases#dora
One-click install
npx skills add https://github.com/archyl-com/agent-skills --skill archyl-changelog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: archyl-changelog
Source: https://github.com/archyl-com/agent-skills/tree/main/plugins/archyl-developer/skills/archyl-changelog
Command: npx skills add https://github.com/archyl-com/agent-skills --skill archyl-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coalesces scattered architecture data (change history, ADRs, releases, drift, and change requests) into a single, readable changelog to track evolution over a chosen time window.

Core Features & Use Cases

  • Aggregates data from change history, ADRs, releases, change requests, version diffs, and drift metrics into a structured markdown timeline.
  • Filter by time range (e.g., sprint, quarter) and by element or team to focus on relevant changes.
  • Produce release notes, ADR updates, and drift insights in a coherent narrative for architecture reviews.

Quick Start

Run this skill against your target project for the desired date range to generate a markdown changelog.

Frequently Asked Questions about archyl-changelog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an architecture changelog from scattered ADRs and release data?▼

To generate an architecture changelog, aggregate change history, ADRs, releases, change requests, version diffs, and drift scores into a structured markdown timeline. The consolidated narrative tracks architectural evolution over your chosen time window.

What is the best way to track architecture drift across a sprint or quarter?▼

Tracking architecture drift across a sprint or quarter requires aggregating drift scores and change history into a structured timeline. Filtering by time range, element, or team focuses the report on relevant architectural changes and drift insights.

Can I filter architecture change requests by team or element for release notes?▼

Yes, you can filter architecture change requests by team, element, or change type to produce focused release notes. The filtering applies to sprint, quarter, or release periods, generating either a timeline or a detailed report.

Does this approach work with existing Change History APIs and ADR repositories?▼

Yes, this approach integrates directly with Change History APIs, ADRs, releases, CRs, and drift data sources. Connecting these inputs allows you to coalesce scattered architecture data into a single readable changelog.

What data sources do I need to produce a structured architecture timeline?▼

To produce a structured architecture timeline, you need change history, ADRs, releases, change requests, version diffs, and drift metrics. These sources are aggregated to create a coherent narrative for architecture reviews.

Related Skills

Explore More Software Engineering Skills→
Morris-UTRUSTMorris-UTRUST

data-research

Extracts structured data from emails, websites, and APIs into canonical trackers via parameterized recipes.

Community
Advanced
AEtherlight-aiAEtherlight-ai

sprint-plan

Generate TOML sprint definitions and Git workflow artifacts for Agile sprint planning.

Official
Intermediate
MFS-codeMFS-code
8

document-release

Audit markdown documentation against code diffs and update release notes.

Community
Advanced
o9nno9nn

release-changelog

Compile git commits, PR summaries, and change notes into a standardized changelog document.

Official
Intermediate