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.

agent-skill-authoring-best-practices

Designs, creates, reviews, and improves reusable AI agent skills with proportional depth, precise activation, progressive disclosure, supporting references, assets or scripts, safety boundaries, validation, and realistic evaluation. Use when asked to build a skill, strengthen a shallow skill, design a reusable agent workflow, or review skill quality and portability.

coding-best-practices-router

Routes ambiguous, repository-wide, or mixed-technology coding requests to the smallest useful set of installed coding best-practices skills. Use when the target technology is unclear, work spans multiple supported technologies, or the user asks which catalog skill applies. Do not use when one specialized skill already clearly matches.

commit-message-writer

Drafts, reviews, and plans clear Conventional Commit titles and descriptions from repository evidence. Use when asked to write or improve a commit message, choose feat/fix/chore or another type, map commit prefixes to repository labels, summarize staged changes, or split mixed changes into logical commits.

github-actions-best-practices

Creates, reviews, refactors, and secures GitHub Actions workflows, reusable workflows, and custom or composite actions. Use for files under .github/workflows, action.yml or action.yaml, action versioning, workflow dependency lockfiles, SHA pinning, permissions, OIDC, Dependabot, caching, matrices, concurrency, artifacts, and CI/CD workflow design.

go-best-practices

Creates, reviews, refactors, and tests idiomatic Go applications, packages, modules, and Go CI workflows. Use for .go files, go.mod, project structure, APIs, interfaces, errors, context, concurrency, logging, tests, fuzzing, benchmarks, dependencies, or GitHub Actions that format, vet, build, race-test, and scan Go.

powershell-best-practices

Creates, reviews, and refactors PowerShell 7.6+ scripts, modules, functions, pipeline behavior, errors, ShouldProcess support, tests, and PowerShell CI workflows. Use for PowerShell code, module design, Pester, PSScriptAnalyzer, formatting, documentation validation, concurrency, or GitHub Actions that validate PowerShell.

pull-request-description-writer

Writes concise, reviewer-focused pull request titles and descriptions from local branch changes. Use when asked to summarize a branch for a PR, draft or improve a PR description, explain changes to reviewers, or identify testing, risks, breaking changes, migrations, and follow-up work for code review.

python-best-practices

Applies modern Python coding standards for maintainable .py files, CLIs, tests, package structure, and Python CI workflows. Use when user asks to write, review, or refactor Python; add typing, logging, tests, or a CLI; improve concurrency or project layout; or create Python formatting, validation, build, and test automation.

terraform-best-practices

Creates, edits, reviews, explains, and refactors Terraform .tf and .tfvars code, modules, providers, state, CI checks, and project layouts. Use when user asks to "write Terraform", "review Terraform", "fix tf files", "add a module", "configure providers", "validate Terraform", or "plan infrastructure".

typescript-best-practices

Creates, reviews, refactors, and tests maintainable TypeScript applications, libraries, packages, and CI workflows. Use for .ts and .tsx files, tsconfig files, package structure, type design, runtime validation, async behavior, dependency management, tests, builds, or TypeScript GitHub Actions.