New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Cross-Language Coding Standards

by zereight in zereight/gitlab-mcp

Shared reference for naming, function size, complexity and error handling rules that reviewer agents apply across TypeScript, Python, Go, Rust, Java, C# and Swift.

MITAuto-check passedDevelopment

Install Cross-Language Coding Standards

skills CLI
$ npx skills add zereight/gitlab-mcp --skill coding-standards -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install zereight/gitlab-mcp coding-standards --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/zereight/gitlab-mcp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/coding-standards .claude/skills/coding-standards && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
coding-standards
GitHub stars
2k
Used in
1 other repo
Token cost
~1.4k tokens
SKILL.md length
522 words
Files
1
Skills in repo
24
Repo updated
First seen
Licence
MIT

At a glance

Shared reference for naming, function size, complexity and error handling rules that reviewer agents apply across TypeScript, Python, Go, Rust, Java, C# and Swift.

  • Checking naming rules for variables, functions, constants and types
  • SKILL.md covers Naming Conventions, Function Design, Error Handling and Code Structure, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Reviewing code against a shared style baseline

What it does

This is a shared, cross-language coding standards reference that language-specific reviewer agents embed and that other agents cite as the style baseline. It opens with a naming table for variables, functions and constants in TypeScript and JavaScript, Python, Go, Rust, Java, C# and Swift, then sets PascalCase for classes and types everywhere, is, has, can or should prefixes for booleans and plural nouns for collections. It also lists what to avoid, such as single-letter names outside loops, needless abbreviations and redundant type suffixes.

Function design rules give a guideline of 50 lines with anything over 80 always split, one job per function, no more than 3 parameters before switching to an options object, cyclomatic complexity of 10 or less with over 15 a mandatory refactor target, and nesting of 3 levels or less, flattened with early returns. Error handling rules forbid silently swallowing errors, require context in messages, say to handle or re-throw but never both and never neither, prefer typed errors in TypeScript and forbid bare except clauses in Python.

When your agent uses it

  • Checking naming rules for variables, functions, constants and types
  • Reviewing code against a shared style baseline
  • Deciding when a function is too long or too complex to leave as it is
  • Reviewing error handling for swallowed or context-free errors

Example prompts

  • “Tell me the naming convention for constants in Rust compared with Go.”
  • “Review this handler against the coding standards and flag anything over the function limits.”
  • “Rewrite this nested function using early returns and check its error handling.”

What it can do on your machine

Read from SKILL.md and the folder at commit 0109168. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cross-Language Coding Standards loads about 1.4k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 522 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~61
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from zereight/gitlab-mcp at commit 0109168, republished under its MIT licence (© zereight). 522 words, ~1,370 tokens.

Download SKILL.mdSave it as .claude/skills/coding-standards/SKILL.md (or your agent's skills folder).
name
coding-standards
description
Canonical cross-language coding standards reference. Shared rules embedded by reviewer agents. Activate when: viewing coding standards, checking naming rules, reviewing style baseline, consulting style guide, what are the rules.
argument-hint
[optional: specific topic — naming | functions | errors | anti-patterns]

Coding Standards

D9 Canonical Reference. This is the single source of truth for cross-language coding standards. Language-specific reviewers (@typescript-reviewer, @python-reviewer, etc.) embed these rules. Agents cite this skill as "See also: /coding-standards."

Naming Conventions

Variables & Functions
LanguageVariablesFunctionsConstants
TypeScript / JavaScriptcamelCasecamelCaseSCREAMING_SNAKE_CASE
Pythonsnake_casesnake_caseSCREAMING_SNAKE_CASE
GocamelCasecamelCaseCamelCase (exported)
Rustsnake_casesnake_caseSCREAMING_SNAKE_CASE
JavacamelCasecamelCaseSCREAMING_SNAKE_CASE
C#camelCasePascalCasePascalCase
SwiftcamelCasecamelCasecamelCase
Classes / Types / Interfaces

PascalCase — all languages, no exceptions.

Booleans

Prefix with is, has, can, should: isLoading, hasError, canEdit, shouldRefresh.

Collections

Plural nouns: users, errors, items — not userList, errorArray.

Avoid
  • Single-letter variables outside loop counters (i, j, k are OK in loops)
  • Abbreviations that save under 3 characters: usr → user, mgr → manager
  • Redundant type names: UserInterface, UserClass, UserObject → just User

Function Design

  • Max length: 50 lines (firm guideline; > 80 lines is always a split target)
  • Single responsibility: one function, one job — if "and" appears in the description, split it
  • Max parameters: 3; beyond that, use an options/config object
  • Cyclomatic complexity: ≤ 10; > 15 is a mandatory refactor target
  • Nesting depth: ≤ 3 levels; use early returns to flatten
Early Return Pattern (preferred)
typescript
// BEFORE — deep nesting
function handle(input) {
  if (input) {
    if (input.valid) {
      return process(input);
    }
  }
  return null;
}

// AFTER — early returns
function handle(input) {
  if (!input || !input.valid) return null;
  return process(input);
}

Error Handling

  • Never swallow errors silently: catch (e) {} is always wrong
  • Error messages must contain context: "Failed to fetch user id=42" not "Error"
  • Propagate or handle: either handle the error at the right level OR re-throw it — never both and never neither
  • Typed errors (TypeScript): class NotFoundError extends Error { constructor(id: string) ... } not generic new Error
  • Python exceptions: catch specific exception types; bare except: is forbidden
  • Go errors: always check returned errors; use errors.Is()/errors.As() for comparison
  • Rust results: use ? for propagation; no .unwrap() in library code

Code Structure

Immutability-First
  • const over let (JS/TS); val over var (Swift/Kotlin); final where appropriate
  • Mark fields readonly when not reassigned after construction
  • Prefer immutable data structures for function arguments
No Magic Numbers
typescript
// BAD
if (retries > 3) { ... }
setTimeout(fn, 5000);

// GOOD
const MAX_RETRIES = 3;
const POLL_INTERVAL_MS = 5000;
if (retries > MAX_RETRIES) { ... }
setTimeout(fn, POLL_INTERVAL_MS);
Show full SKILL.md (216 more words)Show less
No Commented-Out Code

If it is dead → delete it (git history preserves it). If it is needed soon → it should be in a branch. If it explains a non-obvious decision → keep it as a comment, not commented-out code.

Anti-Patterns Reference

PatternSeverityReason
Mutable global stateHIGHUnpredictable side effects; hides dependencies
Promise not awaitedHIGHUnhandled async errors silently swallowed
any in TypeScriptMEDIUMBypasses type safety across call boundaries
console.log in production codeLOWLog noise; potential data leak in sensitive contexts
TODO without issue tracker referenceLOWBecomes permanent tech debt
God ObjectHIGHSingle class with too many responsibilities
Magic numbers inlineMEDIUMUnclear intent; maintenance hazard
Copy-paste logicMEDIUMSilent divergence over time
Catching and re-throwing without contextMEDIUMStack traces lose meaning
Nested ternary operatorsMEDIUMUnreadable; use if/else or switch instead

SOLID Principles Checklist

  • Single Responsibility: does this class/function do exactly one thing?
  • Open/Closed: extend via composition/interfaces, not inheritance modification?
  • Liskov Substitution: can a subtype always replace the base type without breaking callers?
  • Interface Segregation: no fat interfaces — clients should not depend on methods they don't use?
  • Dependency Inversion: depend on abstractions (interfaces), not concretions?

See Also

  • @code-reviewer — applies these rules during code review
  • @typescript-reviewer, @python-reviewer, etc. — language-specific rules with these as baseline
  • @security-reviewer — security-specific standards (OWASP, secrets, crypto)

© zereight, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .github/skills/coding-standards of zereight/gitlab-mcp.

Open the folder on GitHubat commit 0109168

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in zereight/gitlab-mcp, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Cross-Language Coding Standards next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cross-Language Coding Standards compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cross-Language Coding Standards this skillzereight/gitlab-mcp2k1 repos~1.4kAutomated safety check: PassMIT
Supercovsupercorp-ai/supercov1501 repos~415Automated safety check: PassMIT
Code Reviewerjewbetcha/opentrace1162 repos~1.1kAutomated safety check: NotesMIT
Coding Agentmastra-ai/mastra29k—~2.3kAutomated safety check: PassCustom licence
Strict Programming Practicescode-yeongyu/oh-my-openagent70k—~9.5kAutomated safety check: PassCustom licence
Code Review Excellenceandrew-yangy/gru-ai155—~1.7kAutomated safety check: NotesMIT

Similar skills

  • Supercov

    supercorp-ai/supercov

    Measures test coverage and code quality in a repository with the supercov CLI, and turns what it finds into small, focused tests or fixes.

    150 GitHub starsUsed in 1 repo~415 tokens
    Testing & QAAuto-check passed

  • Code Reviewer

    jewbetcha/opentrace

    Comprehensive code review skill for TypeScript, JavaScript, Python, Swift, Kotlin, Go.

    116 GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check: notes

  • Coding Agent

    mastra-ai/mastra

    Authoring playbook for building agents that write, edit, review, or refactor code.

    29k GitHub stars~2.3k tokensUpdated today
    DevelopmentAuto-check passed

  • Strict Programming Practices

    code-yeongyu/oh-my-openagent

    Applies strict, type-first coding rules for Python, Rust, TypeScript and Go, loading the matching language reference before the agent writes or edits any code.

    70k GitHub stars~9.5k tokensUpdated today
    DevelopmentAuto-check passed

  • Code Review Excellence

    andrew-yangy/gru-ai

    Provides comprehensive code review guidance for React 19, Vue 3, Rust, TypeScript, Java, Python, and C/C++.

    155 GitHub stars~1.7k tokensUpdated 7 mo ago
    DevelopmentAuto-check: notes

  • Code Reviewer

    LeoYeAI/openclaw-master-skills

    Code review automation for TypeScript, JavaScript, Python, Go, Swift, Kotlin.

    2.2k GitHub starsUsed in 1 repo~1.2k tokens
    DevelopmentAuto-check passed

More from zereight/gitlab-mcp

All 24 skills in this repo

  • OMG Mode Canceller

    zereight/gitlab-mcp

    Detects which autonomous OMG mode is currently active - Autopilot, Ralph, Ultrawork, UltraQA, Team or Self-Improve - and shuts it down cleanly.

    2k GitHub starsUsed in 1 repo~690 tokens
    Auto-check passed

  • CCG Tri-Model Orchestration

    zereight/gitlab-mcp

    Runs a task through Codex and Gemini CLIs in parallel alongside Claude, then synthesizes the three outputs into one answer with agreements and conflicts called out.

    2k GitHub starsUsed in 1 repo~657 tokens
    Auto-check passed

  • Remember Project Knowledge

    zereight/gitlab-mcp

    Sorts what you learned in a session into the right memory surface, filtering out ephemeral notes and duplicates before anything is stored.

    2k GitHub starsUsed in 1 repo~846 tokens
    Auto-check passed

  • Pre-Commit Security Scan

    zereight/gitlab-mcp

    Runs a fast security sweep of recent code changes before a commit or PR, checking for leaked secrets, vulnerable dependencies, unsafe input handling and auth gaps.

    2k GitHub starsUsed in 1 repo~859 tokens
    Auto-check: notes

  • Skill Inventory Stocktake

    zereight/gitlab-mcp

    Audits a project's skill directories for broken frontmatter, missing template sync and quality gaps, then produces a health report of what needs fixing.

    2k GitHub starsUsed in 1 repo~1k tokens
    Auto-check passed

  • OMG Mode Status

    zereight/gitlab-mcp

    Reports which OMG modes are active, such as autopilot, ralph, team, ultraqa and self-improve, with phase, story or cycle progress read from their state files.

    2k GitHub starsUsed in 1 repo~441 tokens
    Auto-check passed

Works with

Categories

Questions about Cross-Language Coding Standards

What does Cross-Language Coding Standards do?

Shared reference for naming, function size, complexity and error handling rules that reviewer agents apply across TypeScript, Python, Go, Rust, Java, C# and Swift. This is a shared, cross-language coding standards reference that language-specific reviewer agents embed and that other agents cite as the style baseline. It opens with a naming table for variables, functions and constants in TypeScript and JavaScript, Python, Go, Rust, Java, C# and Swift, then sets PascalCase for classes and types everywhere, is, has, can or should prefixes for booleans and plural nouns for collections.

When should I use Cross-Language Coding Standards?

Cross-Language Coding Standards fits situations like: checking naming rules for variables, functions, constants and types; reviewing code against a shared style baseline; deciding when a function is too long or too complex to leave as it is; reviewing error handling for swallowed or context-free errors.

How do I install Cross-Language Coding Standards in Claude Code?

Run `npx skills add zereight/gitlab-mcp --skill coding-standards -a claude-code`. Or copy the skill folder (.github/skills/coding-standards in zereight/gitlab-mcp) into .claude/skills/coding-standards in your project. Claude Code loads it when a task matches its description.

How do I install Cross-Language Coding Standards in Codex?

Run `npx skills add zereight/gitlab-mcp --skill coding-standards -a codex`. Or copy the skill folder (.github/skills/coding-standards in zereight/gitlab-mcp) into .agents/skills/coding-standards in your project. Codex loads it when a task matches its description.

Can I use Cross-Language Coding Standards in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add zereight/gitlab-mcp --skill coding-standards -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/coding-standards, .gemini/skills/coding-standards, .github/skills/coding-standards and .opencode/skills/coding-standards in your project.

What does Cross-Language Coding Standards need to run?

SKILL.md names no scripts, command-line tools or credentials: Cross-Language Coding Standards is instructions for the agent only.

Does Cross-Language Coding Standards access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Cross-Language Coding Standards safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Cross-Language Coding Standards use?

Cross-Language Coding Standards is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cross-Language Coding Standards use?

About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Cross-Language Coding Standards?

Skills that share tags, products or a category with Cross-Language Coding Standards: Supercov (supercorp-ai/supercov, 150 stars), Code Reviewer (jewbetcha/opentrace, 116 stars), Coding Agent (mastra-ai/mastra, 29k stars) and Strict Programming Practices (code-yeongyu/oh-my-openagent, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cross-Language Coding Standards?

zereight (a GitHub user) maintains it in zereight/gitlab-mcp, which has 2,029 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on October 6, 2026.

Source: zereight/gitlab-mcp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.