Skip to content

jschronicles/coding-best-practices

v0.6.0MIT

Reusable, provider-neutral best-practices skills for writing, reviewing, and maintaining code, infrastructure, and automation.

GitHub

Coding Best Practices

Provider-neutral agent skills for writing, reviewing, and maintaining code, infrastructure, and automation.

Skills

Included skills

  • agent-skill-authoring-best-practices
  • coding-best-practices-router
  • commit-message-writer
  • go-best-practices
  • github-actions-best-practices
  • python-best-practices
  • powershell-best-practices
  • pull-request-description-writer
  • terraform-best-practices
  • typescript-best-practices

Each skill is maintained once under skills/. Product-specific manifests expose those same canonical skill directories rather than maintaining copies.

The router handles ambiguous, repository-wide, workflow, and mixed-technology requests. It selects the smallest useful set of specialized skills from project evidence, then loads those skills before acting. Requests that clearly target one technology can use its specialized skill directly.

Codex CLI and ChatGPT desktop app

Add the GitHub repository as a marketplace:

codex plugin marketplace add JSChronicles/coding-best-practices --ref main

Open /plugins, select the Coding Best Practices marketplace, and install the plugin. Start a new chat after installation or an upgrade.

Refresh configured marketplaces with:

codex plugin marketplace upgrade

Claude Code

Add the repository as a marketplace and install the plugin:

/plugin marketplace add JSChronicles/coding-best-practices
/plugin install coding-best-practices@coding-best-practices

Start a new Claude Code session after installation or an upgrade.

Other agents

Agents that support the Agent Skills layout can install individual directories from skills/ at user or project scope. Installation locations and update mechanisms vary by agent. The skill content avoids provider-specific terminology so the same package can be adapted without changing its instructions.

Contributing

Keep each skill focused and provider-neutral. Put detailed, conditional guidance in references/, link it from SKILL.md, and validate changed skills before publishing a new package version.

Run the repository validator before opening a pull request:

uv run scripts/validate_skills.py

The validator checks every skill's frontmatter, author and version metadata, local Markdown links, optional agents/openai.yaml, and synchronized plugin manifests. The same command runs in GitHub Actions for relevant pull requests and pushes to main.

After changing a workflow or action dependency, regenerate and verify the workflow lockfile:

gh actions-lock
gh actions-lock --verify-local