setup-coding-standards
Write CODING_STANDARDS.md at the repo root when it has none: the baseline plus the repo's conventions verified from code. An existing standards file is left untouched.
How do I install this agent skill?
npx skills add https://github.com/hu3rror/my-skills --skill setup-coding-standardsIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill initializes a coding standards file for a project by combining a local baseline with conventions discovered from the repository's code. It follows secure practices by prioritizing actual code logic over potentially misleading comments and performs no network operations or sensitive data access.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
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.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/hu3rror/my-skills/setup-coding-standards">View setup-coding-standards on skillZs</a>