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

archyl-postship

Analyze shipped changes and update C4 models, ADRs, and API contracts.

1|Updated Mar 28, 2026
Search Tags:#architecture#documentation#ADR#drift#C4-model#change-requests#post-ship
One-click install
npx skills add https://github.com/archyl-com/agent-skills --skill archyl-postship
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: archyl-postship
Source: https://github.com/archyl-com/agent-skills/tree/main/plugins/archyl-developer/skills/archyl-postship
Command: npx skills add https://github.com/archyl-com/agent-skills --skill archyl-postship

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After code is shipped, you auto-update Archyl's C4 model, ADRs, API contracts, event channels, and architecture relationships to reflect the latest system state, ensuring architecture documentation stays in sync with implementation.

Core Features & Use Cases

  • Analyze shipped changes (diffs, feature releases, and refactors) to determine architectural updates.
  • Update the C4 model, ADRs, API contracts, event channels, and documented relationships automatically.
  • Create Architecture Change Requests for human review when non-trivial updates are detected.

Quick Start

Run archyl-postship after shipping a feature to synchronize documentation across architecture artifacts.

Frequently Asked Questions about archyl-postship

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

FAQPage Schema
How do I auto-update architecture documentation after shipping code?▼

To auto-update architecture documentation after shipping, you can run this Skill to analyze shipped changes and automatically synchronize the C4 model, ADRs, and API contracts with the latest implementation state.

What is the best way to keep ADRs and C4 models in sync with shipped features?▼

Keeping ADRs and C4 models in sync with shipped features requires analyzing code diffs and refactors post-ship. This Skill computes deltas between shipped changes and existing architecture artifacts to generate automated documentation updates.

How do architecture change requests work for major refactors?▼

Architecture change requests for major refactors are generated automatically when non-trivial updates are detected. The Skill analyzes the shipped changes and creates these requests for human review to ensure documentation accuracy.

Do I need existing API contracts and a C4 model to compute post-ship documentation deltas?▼

Yes, you need existing API contracts, a C4 model, event channels, and an ADR repository. The Skill requires access to these current architecture artifacts to accurately compute deltas and update relationships after shipping.

Can I synchronize API contracts and event channels automatically after a release?▼

Yes, you can synchronize API contracts and event channels automatically after a release. The Skill coordinates updates across these architecture artifacts by analyzing the shipped feature or refactor changes.

What types of shipped changes are supported for updating architecture documentation?▼

Supported shipped changes for updating architecture documentation include feature releases, major refactors, and API or event-flow changes. The Skill analyzes these specific change types to determine the necessary architectural updates.

Related Skills

Explore More Software Engineering Skills→
LinoWhyLinoWhy

create-architecture-documentation

Generate C4 or arc42 architecture documentation from codebases and existing documentation.

Community
Intermediate
ZhmYeZhmYe
1

obsidian-change-trace

Maintain Obsidian change-trace notes for Sandrone workspaces.

Community
Advanced
cropsggcropsgg
15

document-release

Audit release documentation and map Diataxis coverage against shipped code.

Community
Advanced
coff33ninjacoff33ninja

adr-and-documentation

Manage Architecture Decision Records and synchronize documentation with codebase changes.

Community
Intermediate