coding-standards

Reference cross-language coding standards for naming, error handling, and structure.

153|12|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/jmstar85/oh-my-githubcopilot --skill coding-standards-jmstar85
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-standards
Source: https://github.com/jmstar85/oh-my-githubcopilot/tree/main/.github/skills/coding-standards
Command: npx skills add https://github.com/jmstar85/oh-my-githubcopilot --skill coding-standards-jmstar85

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canonical cross-language coding standards provide a single source of truth for naming conventions, error handling, and code structure, helping reviewers and teams maintain consistency across languages.

Core Features & Use Cases

  • Language-agnostic guidelines covering naming conventions, class/type rules, boolean naming, collections, and anti-patterns.
  • Serves as baseline references for code reviews, onboarding, and cross-team alignment for TypeScript/JavaScript, Python, Go, Rust, Java, C#, and Swift.
  • Example use: a reviewer cites "See also: /coding-standards" during pull requests to ensure style compliance.

Quick Start

Consult coding-standards during code reviews and when implementing cross-language rules to ensure consistent naming, structure, and error handling.

Frequently Asked Questions about coding-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain consistent coding standards across multiple programming languages?

To maintain consistent coding standards across multiple programming languages, apply language-agnostic guidelines that unify naming conventions, error handling, and code structure. This provides a single source of truth for cross-team alignment during code reviews and onboarding.

What are common naming conventions and anti-patterns for TypeScript, Python, and Go?

Common naming conventions and anti-patterns for TypeScript, Python, and Go involve following language-agnostic guidelines for class/type rules, boolean naming, and collections. Codifying these rules establishes a baseline style alignment to improve readability and maintainability across teams.

How do I standardize error handling and code structure for cross-language code reviews?

Standardize error handling and code structure for cross-language code reviews by citing a canonical coding-standards reference during pull requests. This ensures style compliance and consistent implementation across TypeScript, JavaScript, Python, Go, Rust, Java, C#, and Swift.

Does this coding standards reference work for Rust, Java, C#, and Swift?

Yes, this coding standards reference works for Rust, Java, C#, and Swift. It provides a comprehensive cross-language reference spanning code reviews, onboarding, and baseline style alignment to improve code quality for these specific languages.

What's the best way to align baseline code style for a polyglot engineering team?

The best way to align baseline code style for a polyglot engineering team is to adopt canonical cross-language coding standards. This unifies naming conventions and error handling across multiple languages, serving as a single source of truth for consistent implementation.