aiskillstore/marketplace / skills/89jobrien/global-standards
global-standards
VerifiedProject-wide coding standards and conventions specialist. Use PROACTIVELY when writing code, making architectural decisions, or establishing project conventions. Covers coding style, commenting, error handling, validation, tech stack consistency, and project conventions across all languages and frameworks.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.0 KB |
| references/coding-style.md | markdown | 1.2 KB |
| references/commenting.md | markdown | 1.1 KB |
| references/conventions.md | markdown | 1.6 KB |
| references/error-handling.md | markdown | 1.4 KB |
| references/tech-stack.md | markdown | 1.2 KB |
| references/validation.md | markdown | 1.2 KB |
| skill-report.json | config | 19.8 KB |
skill-report.json
View on GitHub{
"schema_version": "2.0",
"meta": {
"generated_at": "2026-07-05T12:27:52.839Z",
"slug": "89jobrien-global-standards",
"source_url": "https://github.com/89jobrien/steve/tree/main/steve/skills/global-standards",
"source_ref": "main",
"model": "codex",
"analysis_version": "3.0.0",
"source_type": "community",
"content_hash": "b5a9ab440fa48a29c98b2fd59aaff6a09fd5ae6a4879d89555a96f53ce7d8895",
"tree_hash": "f8cae66189da287c3ace3beb9bd7b582d312aa4c35b3e437ad39a2fefb5e701b",
"provenance": {
"model_effective": "codex",
"fallback_chain": [
{
"agent": "codex",
"outcome": "success"
}
],
"analysis_version": "3.0.0"
}
},
"skill": {
"name": "global-standards",
"description": "Guides Claude, Codex, and Claude Code to apply consistent coding style, commenting, error handling, validation, technology choices, and project conventions across a codebase.",
"summary": "Apply project-wide coding standards and conventions across development work.",
"icon": "📦",
"version": "1.0.2",
"author": "Joseph OBrien",
"license": "MIT",
"tags": [
"coding-standards",
"code-review",
"validation",
"documentation",
"architecture"
],
"supported_tools": [
"claude",
"codex",
"claude-code"
],
"risk_factors": [
"external_commands"
],
"category": "coding"
},
"security_audit": {
"risk_level": "safe",
"is_blocked": false,
"safe_to_publish": true,
"analysis_status": "ok",
"summary": "All fourteen static findings are false positives caused by Markdown formatting or benign standards documentation. No prompt-injection, command-execution, secret-access, or data-exfiltration intent was found in the reviewed files.",
"remediation": [],
"risk_factor_evidence": [
{
"factor": "external_commands",
"evidence": [
{
"file": "SKILL.md",
"line_start": 187,
"line_end": 187
},
{
"file": "SKILL.md",
"line_start": 188,
"line_end": 188
},
{
"file": "SKILL.md",
"line_start": 189,
"line_end": 189
},
{
"file": "SKILL.md",
"line_start": 190,
"line_end": 190
},
{
"file": "SKILL.md",
"line_start": 191,
"line_end": 191
},
{
"file": "SKILL.md",
"line_start": 192,
"line_end": 192
}
]
}
],
"static_findings": [
{
"id": "blocker:references/coding-style.md:48:system-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "System reconnaissance",
"file": "references/coding-style.md",
"line_start": 48,
"line_end": 48,
"snippet": "- Avoid code duplication"
},
{
"id": "sensitive:references/conventions.md:50:environment-file-access",
"category": "sensitive",
"severity": "high",
"pattern": "Environment file access",
"file": "references/conventions.md",
"line_start": 50,
"line_end": 50,
"snippet": "- Use .env files for local development"
},
{
"id": "sensitive:references/conventions.md:53:environment-file-access",
"category": "sensitive",
"severity": "high",
"pattern": "Environment file access",
"file": "references/conventions.md",
"line_start": 53,
"line_end": 53,
"snippet": "- Provide .env.example template"
},
{
"id": "blocker:references/error-handling.md:41:system-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "System reconnaissance",
"file": "references/error-handling.md",
"line_start": 41,
"line_end": 41,
"snippet": "- Avoid technical jargon"
},
{
"id": "blocker:references/validation.md:47:system-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "System reconnaissance",
"file": "references/validation.md",
"line_start": 47,
"line_end": 47,
"snippet": "- Check sufficient balance, valid dates, permissions"
},
{
"id": "external_commands:SKILL.md:187:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 187,
"line_end": 187,
"snippet": "- **`references/coding-style.md`** - Detailed coding style guidelines, naming conventions, formattin"
},
{
"id": "external_commands:SKILL.md:188:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 188,
"line_end": 188,
"snippet": "- **`references/commenting.md`** - Commenting best practices, docstring standards, when to comment"
},
{
"id": "external_commands:SKILL.md:189:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 189,
"line_end": 189,
"snippet": "- **`references/error-handling.md`** - Error handling patterns, exception hierarchies, logging strat"
},
{
"id": "external_commands:SKILL.md:190:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 190,
"line_end": 190,
"snippet": "- **`references/validation.md`** - Validation patterns, schema definitions, security considerations"
},
{
"id": "external_commands:SKILL.md:191:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 191,
"line_end": 191,
"snippet": "- **`references/tech-stack.md`** - Technology stack reference, framework patterns, dependency guidel"
},
{
"id": "external_commands:SKILL.md:192:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 192,
"line_end": 192,
"snippet": "- **`references/conventions.md`** - Project conventions, file structure, git workflows, CI/CD standa"
},
{
"id": "sensitive:SKILL.md:181:environment-file-access",
"category": "sensitive",
"severity": "high",
"pattern": "Environment file access",
"file": "SKILL.md",
"line_start": 181,
"line_end": 181,
"snippet": "**Applies to:** Configuration files (.env, package.json, requirements.txt, pyproject.toml, Dockerfil"
},
{
"id": "blocker:SKILL.md:40:system-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "System reconnaissance",
"file": "SKILL.md",
"line_start": 40,
"line_end": 40,
"snippet": "- Extracting reusable logic to avoid duplication"
},
{
"id": "blocker:SKILL.md:71:system-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "System reconnaissance",
"file": "SKILL.md",
"line_start": 71,
"line_end": 71,
"snippet": "- Avoid comments that restate what code does"
}
],
"finding_verdicts": [
{
"id": "blocker:references/coding-style.md:48:system-reconnaissance",
"verdict": "false_positive",
"confidence": 0.98,
"reason": "Line 48 is style guidance to avoid code duplication. It does not request host inspection, credential discovery, or system reconnaissance."
},
{
"id": "sensitive:references/conventions.md:50:environment-file-access",
"verdict": "false_positive",
"confidence": 0.94,
"reason": "The line recommends using .env files for local development and is paired with guidance not to commit secrets. It does not read, expose, or request environment file contents."
},
{
"id": "sensitive:references/conventions.md:53:environment-file-access",
"verdict": "false_positive",
"confidence": 0.96,
"reason": "The .env.example instruction is a safe documentation pattern for non-secret templates. No secret access or exfiltration behavior is present."
},
{
"id": "blocker:references/error-handling.md:41:system-reconnaissance",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "Line 41 tells authors to avoid technical jargon in user-facing errors. This is documentation quality guidance, not reconnaissance."
},
{
"id": "blocker:references/validation.md:47:system-reconnaissance",
"verdict": "false_positive",
"confidence": 0.97,
"reason": "The line lists ordinary business-rule validation examples such as balance, dates, and permissions. It does not instruct system probing or information gathering."
},
{
"id": "external_commands:SKILL.md:187:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "The backticks are Markdown formatting around a local reference filename. There is no executable shell, Ruby code, or command interpolation."
},
{
"id": "external_commands:SKILL.md:188:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "The backticks are Markdown formatting around a local documentation path. This is not shell execution or command construction."
},
{
"id": "external_commands:SKILL.md:189:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "The line uses inline Markdown code for a reference file path. No runtime command execution behavior is present."
},
{
"id": "external_commands:SKILL.md:190:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "The detected backticks delimit a documentation filename. The skill contains no Ruby shell backtick execution at this location."
},
{
"id": "external_commands:SKILL.md:191:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "This is a Markdown bullet pointing to a local reference file. It does not execute external commands or pass user input to a shell."
},
{
"id": "external_commands:SKILL.md:192:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "The backticks are only inline code formatting around references/conventions.md. There is no command execution surface."
},
{
"id": "sensitive:SKILL.md:181:environment-file-access",
"verdict": "false_positive",
"confidence": 0.95,
"reason": "The line lists configuration files as areas where project conventions apply. It does not instruct the agent to read .env values or disclose secrets."
},
{
"id": "blocker:SKILL.md:40:system-reconnaissance",
"verdict": "false_positive",
"confidence": 0.98,
"reason": "The line recommends extracting reusable logic to reduce duplication. It is coding-style guidance, not a request to inspect the system."
},
{
"id": "blocker:SKILL.md:71:system-reconnaissance",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "The line advises against comments that restate code behavior. This is commenting guidance with no reconnaissance or sensitive-data intent."
}
],
"semantic_findings": [],
"critical_findings": [],
"high_findings": [],
"medium_findings": [],
"low_findings": [],
"dangerous_patterns": [],
"files_scanned": 7,
"total_lines": 629,
"audit_model": "codex",
"audited_at": "2026-07-05T12:27:52.839Z",
"agent_auto_install_policy": "allowed",
"manual_install_policy": "allowed"
},
"content": {
"user_title": "Standardize Project Coding Practices",
"value_statement": "Teams lose time when code style, validation, and workflow decisions vary across files. This skill gives Claude, Codex, and Claude Code consistent standards to apply during development.",
"seo_keywords": [
"Claude",
"Codex",
"Claude Code",
"coding standards",
"project conventions",
"code review",
"input validation",
"error handling",
"documentation standards",
"tech stack consistency"
],
"actual_capabilities": [
"Applies naming, formatting, and structure guidance across common programming languages.",
"Guides comment and docstring decisions with focus on useful context.",
"Recommends error handling patterns for user messages, logging, retries, and cleanup.",
"Promotes client-side and server-side validation with sanitization guidance.",
"Helps keep dependencies, frameworks, file structure, and workflows consistent."
],
"limitations": [
"It provides standards guidance, not automated linting or formatting by itself.",
"It does not replace project-specific rules stored outside the skill files.",
"It cannot verify behavior without access to the target codebase and tests.",
"It gives general guidance that may need adaptation for regulated environments."
],
"use_cases": [
{
"title": "Review a Pull Request",
"description": "Check whether code changes follow naming, comments, validation, and error handling conventions.",
"target_user": "Engineering reviewers"
},
{
"title": "Plan a New Feature",
"description": "Choose patterns for files, dependencies, validation, and error handling before implementation starts.",
"target_user": "Feature developers"
},
{
"title": "Create Team Standards",
"description": "Use the reference files as a baseline for shared coding and workflow conventions.",
"target_user": "Technical leads"
}
],
"prompt_templates": [
{
"title": "Check Basic Style",
"scenario": "Beginner review for a small code change.",
"prompt": "Review this change against the global standards. Focus on names, formatting, comments, and avoidable duplication."
},
{
"title": "Improve Error Handling",
"scenario": "Intermediate review for service or API code.",
"prompt": "Use the global standards to improve error handling. Check user messages, logging, cleanup, retries, and propagation boundaries."
},
{
"title": "Validate Feature Design",
"scenario": "Advanced planning before implementation.",
"prompt": "Evaluate this feature plan against global standards. Cover validation, security boundaries, file structure, dependencies, and framework consistency."
},
{
"title": "Audit Project Conventions",
"scenario": "Advanced repository-wide standards review.",
"prompt": "Audit this repository for global standards alignment. Identify convention gaps, repeated patterns, dependency concerns, and documentation updates."
}
],
"output_examples": [
{
"input": "A pull request adds a new API endpoint with minimal validation.",
"output": [
"Validation should run on both the request boundary and any domain service boundary.",
"Error messages should be clear for users and should avoid leaking internal details.",
"The endpoint should follow the existing route and file naming patterns."
]
},
{
"input": "A developer wants to add a new package for date parsing.",
"output": [
"First check whether the project already has a date utility or approved dependency.",
"Document the reason for a new package if existing tools do not meet the requirement.",
"Add tests for edge cases such as invalid dates and timezone boundaries."
]
},
{
"input": "A team needs shared rules for comments and documentation.",
"output": [
"Comments should explain intent, tradeoffs, and non-obvious behavior.",
"Remove comments that repeat clear code behavior or have become outdated.",
"Public interfaces should include concise documentation for parameters and results."
]
}
],
"best_practices": [
"Load the relevant reference file before making detailed standards decisions.",
"Compare new code with nearby project patterns before adding new abstractions.",
"Run project tests and quality checks after applying standards changes."
],
"anti_patterns": [
"Do not use the skill as a substitute for project-specific requirements.",
"Do not add new dependencies before checking existing tools and conventions.",
"Do not apply generic standards when local code has a clear established pattern."
],
"faq": [
{
"question": "What does this skill help with?",
"answer": "It helps apply consistent coding style, comments, validation, error handling, dependencies, and project workflow conventions."
},
{
"question": "Does it run formatters or linters?",
"answer": "No. It provides guidance, but the agent can still use project tools when available."
},
{
"question": "Can it support different programming languages?",
"answer": "Yes. The guidance is language-neutral and references common patterns across frontend, backend, and infrastructure code."
},
{
"question": "Is it useful for code review?",
"answer": "Yes. It can identify standards issues in naming, structure, comments, validation, and error handling."
},
{
"question": "Does it handle security concerns?",
"answer": "It includes validation, sanitization, dependency, and secret-handling guidance, but it is not a full security scanner."
},
{
"question": "How should teams customize the guidance?",
"answer": "Teams should add project-specific rules and keep the reference files aligned with their actual codebase."
}
]
},
"file_structure": [
{
"name": "references",
"type": "dir",
"path": "references",
"children": [
{
"name": "coding-style.md",
"type": "file",
"path": "references/coding-style.md",
"lines": 57
},
{
"name": "commenting.md",
"type": "file",
"path": "references/commenting.md",
"lines": 58
},
{
"name": "conventions.md",
"type": "file",
"path": "references/conventions.md",
"lines": 93
},
{
"name": "error-handling.md",
"type": "file",
"path": "references/error-handling.md",
"lines": 70
},
{
"name": "tech-stack.md",
"type": "file",
"path": "references/tech-stack.md",
"lines": 61
},
{
"name": "validation.md",
"type": "file",
"path": "references/validation.md",
"lines": 62
}
]
},
{
"name": "SKILL.md",
"type": "file",
"path": "SKILL.md",
"lines": 228
}
]
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |