honk-config-change

Agent Skills › daeuniverse/honk › honk-config-change

honk-config-change

GitHub

处理 honk-config 配置契约变更，包括更新参考文档、运行集成测试及验证核心/出站消费者，确保符合代码规范与发布流程。

.agents/skills/honk-config-change/SKILL.md daeuniverse/honk

Trigger Scenarios

配置契约或解析器变更需要更新配置参考文档涉及 honk-core 或 honk-outbound 消费者的配置修改

Install

npx skills add daeuniverse/honk --skill honk-config-change -g -y

More Options

Non-standard path

npx skills add https://github.com/daeuniverse/honk/tree/main/.agents/skills/honk-config-change -g -y

Use without installing

npx skills use daeuniverse/honk@honk-config-change

指定 Agent (Claude Code)

npx skills add daeuniverse/honk --skill honk-config-change -a claude-code -g -y

安装 repo 全部 skill

npx skills add daeuniverse/honk --all -g -y

预览 repo 内 skill

npx skills add daeuniverse/honk --list

SKILL.md

Frontmatter

{
    "name": "honk-config-change",
    "description": "Use for configuration contracts, parsers, reference docs and their core or outbound consumers."
}

Read first: AGENTS.md, .agents/rules/configuration.md and .agents/rules/test-locations.md.

Steps

Decide which contract changes. For lexical semantics that differ from dae, add a row to doc/en/reference/dialect.md and doc/zh/reference/dialect.md. For a setting, update its reference page under doc/en/reference/ and doc/zh/reference/. A refactor needs no doc change.
Run just test-config or cargo test -p honk-config. Both include unit and integration tests.
If the change reaches honk-core or honk-outbound consumers, run the affected crate tests: cargo test -p honk-outbound, or cargo test -p honk-core. Focused gates and test policy: AGENTS.md, "Current validation guidance" and "Testing instructions".
Update AGENTS.md or the relevant rules file if a convention changed.
PR text: AGENTS.md, "Code style guidelines" (PR bodies).

Checklist

Contract classified; the corresponding documentation step is complete or inapplicable.
honk-config integration tests are included in the crate run.
Affected core or outbound consumers have their crate checks.
Changed conventions are recorded in the root or rules file.
PR text follows "Code style guidelines".