develop-wrapup

Draft bilingual changelogs and audit contracts across ADR, code, and tests.

12|2|Updated Nov 27, 2024
One-click install
npx skills add https://github.com/Pionpill/retikz --skill develop-wrapup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: develop-wrapup
Source: https://github.com/Pionpill/retikz/tree/main/.agents/skills/develop-wrapup
Command: npx skills add https://github.com/Pionpill/retikz --skill develop-wrapup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents inconsistent releases by coordinating the final “wrap-up” phase for alpha feature development, ensuring that the ADR, changelog (zh+en), documentation, and actual behavior agree before any commit is made.

Core Features & Use Cases

  • Drafts release-ready changelog content (zh + en) based on a structured template, without publishing or pushing.
  • Runs an adversarial contract audit by comparing four sources (ADR, changelog draft, mdx/demo, and actual code/tests) to detect promise/description/implementation/behavior mismatches.
  • Gates commits on human acknowledgment: marks ADR as Accepted, updates roadmap checkboxes when applicable, and only then commits the changelog into the repo after explicit “确认”.

Quick Start

Run the develop-wrapup stage after implementation, tests, and docs are complete, then ask the human reviewer to explicitly confirm before any commit sequence is executed.

Frequently Asked Questions about develop-wrapup

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

FAQPage Schema
How do I ensure changelog, ADR, and code consistency before a release commit?

To ensure changelog and ADR consistency before a release commit, run an adversarial contract audit comparing your ADR, changelog draft, mdx/demo, and actual code/tests to detect any mismatches.

What is the best way to draft bilingual release notes without pushing to a repository?

The best way to draft bilingual release notes without pushing is using a structured template to generate zh and en changelog content locally, explicitly avoiding any publish or push actions outside a designated publish skill.

How does human acknowledgment gate git commits during alpha feature wrap-up?

Human acknowledgment gates git commits by requiring an explicit confirmation before executing any commit sequence, ensuring the ADR is marked Accepted and roadmap checkboxes are updated only after human review.

Can I use an adversarial contract audit for end-of-milestone alpha feature completion?

Yes, you can use an adversarial contract audit for end-of-milestone alpha feature completion to validate that declared design contracts in your ADR match documented behavior and implemented tests.

What should I do when ADR descriptions and implemented code behavior do not match?

When ADR descriptions and implemented code behavior do not match, you should route the blocking mismatches into controlled edits and perform re-audits before gating the commit on human acknowledgment.