使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
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.