agentleFS
qiaoshouqingqiaoshouqing/skills/code-standards/SKILL.md

code-standards

Skill1 starsChanged 4 months agoMITView on GitHub

Setup universal code quality standards in your project. Use when the user wants to generate coding standards files (CLAUDE.md, AGENTS.md, GEMINI.md, etc.) or mentions 'code standards', 'code review setup', or similar intent in any language.

17 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use code-review.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • GoogleSkill

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    All other languages → references/code-standards-en.md

    line 28
  2. Distinctive:

    Write the template content directly.

    line 46

“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Code Standards — Universal AI Tool Configuration Generator

Generate code standards files based on Linus Torvalds' "Good Taste" philosophy. Auto-detects AI tools in your project and creates the appropriate configuration files in the user's language.

When to Use

  • User wants to set up coding standards for a project
  • User wants to sync code quality rules across AI coding tools
  • User mentions "code standards", "init claude md", "code review", or equivalent in any language

Instructions for Agent

Step 1: Detect Language & Read Template

Detect the user's language. Read the matching template from this skill's references/ directory:

  • Simplified Chinese → references/code-standards-zh-CN.md
  • Traditional Chinese → references/code-standards-zh-TW.md
  • Japanese → references/code-standards-ja.md
  • All other languages → references/code-standards-en.md

Step 2: Detect AI Tools

PROJECT_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)

[ -d "$PROJECT_ROOT/.cursor" ] && echo "CURSOR"
[ -f "$PROJECT_ROOT/AGENTS.md" ] || [ -d "$PROJECT_ROOT/.codex" ] && echo "CODEX"
[ -f "$PROJECT_ROOT/GEMINI.md" ] || [ -d "$PROJECT_ROOT/.gemini" ] && echo "GEMINI"
[ -d "$PROJECT_ROOT/.github" ] && echo "COPILOT"
[ -d "$PROJECT_ROOT/.windsurf" ] || [ -f "$PROJECT_ROOT/.windsurfrules" ] && echo "WINDSURF"
[ -f "$PROJECT_ROOT/.aider.conf.yml" ] && echo "AIDER"
[ -d "$PROJECT_ROOT/.clinerules" ] || [ -d "$PROJECT_ROOT/.roo" ] && echo "CLINE"

Step 3: Generate Files

Write the template content directly. No confirmation needed — the user invoked this skill, that IS the intent.

Always generate: CLAUDE.md

For each detected tool, also generate:

ToolFileNotes
Cursor.cursor/rules/code-standards.mdcPrepend ---\ndescription: "Linus Torvalds code standards"\nalwaysApply: true\n---\n
CodexAGENTS.mdSame content
GeminiGEMINI.mdSame content
Copilot.github/copilot-instructions.mdmkdir -p .github first
Windsurf.windsurfrulesSame content
AiderCONVENTIONS.mdSame content
Cline/Roo.clinerules/code-standards.mdmkdir -p .clinerules first

Step 4: Report

Report created files in the user's language. Keep it brief.

Response Guidelines

  1. Execute immediately — No confirmation, no "shall I proceed?". Just write.
  2. Unconditionally overwrite existing files — Always overwrite CLAUDE.md and other config files without asking. The invocation is explicit intent to replace.
  3. Respond in user's language — Match the language they used to invoke.
  4. No extra commentary — Detect, write, report. Done.

Error Handling

SituationAction
Not in a git repoUse current directory as root
No tools detectedOnly generate CLAUDE.md
Permission deniedReport error with path
Template not foundFall back to English

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.