Update code-specs with signatures, contracts, and validation rules.
npx skills add https://github.com/yanzhangshuai/wen-yuan --skill update-spec-yanzhangshuai
Please help me install this Agent Skill. Skill: update-spec Source: https://github.com/yanzhangshuai/wen-yuan/tree/main/.agents/skills/update-spec Command: npx skills add https://github.com/yanzhangshuai/wen-yuan --skill update-spec-yanzhangshuai
Keeps code-specs up-to-date by capturing concrete contracts, signatures, payloads, and error behavior after learning from debugging, implementation, or discussion.
Summarize the change and update the applicable code-spec sections, including signatures and error handling.
High-intent search queries and answers about installing and using this skill.
To update executable contracts after a bug fix, you translate the corrected behavior into structured code-spec sections, capturing signatures, payloads, env keys, and error matrices to reflect the new validation rules.
A code-spec is a structured document capturing concrete contracts, signatures, and error behavior. You need to update it after debugging or implementing features that affect infra or cross-layer interfaces to ensure validation rules stay precise.
Document API signatures and validation rules by applying a structured format to your code-specs, detailing Scope/Trigger, Contracts, Validation & Error Matrix, and Good/Base/Bad Cases to capture cross-layer interface behavior comprehensively.
Updating code-specs captures payload and env key changes by enforcing a structured documentation format. It translates implementation learnings into precise contract sections, ensuring signatures and validation rules across affected code paths are accurately recorded.
The best way to maintain executable contracts is enforcing a structured code-spec format that includes Tests Required and Wrong vs Correct checks, ensuring implementation decisions are continuously translated into precise, up-to-date documentation.
You should avoid structured code-spec updates for changes that do not affect infra or cross-layer interfaces. The format targets features, bug fixes, and design decisions requiring explicit signatures, payloads, and validation rules documentation.
XiaSanwRecord executable contracts and coding conventions into .trellis/spec documentation.
Xeron2000Capture executable contracts and coding conventions into seven-section code-spec documents.
C-jcbestCapture executable contracts and coding conventions into .trellis/spec documents.
beomeodevScan code for TAG blocks and generate API docs from function signatures and docstrings.
