使用方法
- 复制安装命令,在自己的智能体环境安装前先检查源码包。
- 从原始文档核对所需工具、凭据和支持的宿主。
- 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/hu3rror/my-skills --skill setup-coding-standards开始前需了解
- 安装不包含模型订阅、API 额度或访问文件的权限。
- 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
仓库原始内容
按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。
Initialize the repo's coding standards
Steps
- Find the repo root. Run
git rev-parse --show-toplevelfrom the cwd; if the repo has no git root, use the cwd. Done when one root path is chosen.
- Check for an existing standards file. Look at the root for
CODING_STANDARDS.mdand near-variants (coding-standards.md, case variants). If one exists: stop, report its path, write nothing. Done when existence is decided.
- Compose the file. Read
references/baseline.md(in this skill's directory) and copy it verbatim as the file's lead; do not rename or restructure its headings. The baseline ends with a marker comment — repo conventions go below that marker, never above it. Then append the repo's conventions you verified from the code as it is now: evidence-cited, nothing invented, and no empty headings. A comment is not evidence — a convention a comment claims must be checked against the code it describes, or dropped. Skip conventions that merely restate what the repo's tooling already enforces — the formatter, linter, or type checker is the single source for those. If you hold no verified conventions, the file is the baseline alone. Done when the baseline part matchesreferences/baseline.mdexactly, every appended line sits below the marker and is verified from the code, and no section is empty.
- Write it to the repo root. Read it back and confirm the content matches what you composed. Done when the file exists and matches.
- Report: the path, what was written (baseline only, or baseline plus which conventions), and that extending the file is a one-place edit: new rules are added here, keeping a single home for each rule.