WooCommerce Code Review
woocommerce/woocommerce
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
Implement, fix, or refactor repository-native code, with attention to behavioral contracts, code shape, implementation economy, and meaningful verification.
Install Coding Standards
$ npx skills add tiramisulabs/seyfert --skill coding-standards -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tiramisulabs/seyfert coding-standards --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/tiramisulabs/seyfert.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/coding-standards .claude/skills/coding-standards && rm -rf skills-srcUse ~/.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/
Install the "coding-standards" agent skill from https://github.com/tiramisulabs/seyfert/tree/main/.agents/skills/coding-standards into .claude/skills/coding-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coding-standards", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/tiramisulabs/seyfert/tree/main/.agents/skills/coding-standardsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add tiramisulabs/seyfert --skill coding-standards -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tiramisulabs/seyfert coding-standards --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tiramisulabs/seyfert.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/coding-standards .agents/skills/coding-standards && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "coding-standards" agent skill from https://github.com/tiramisulabs/seyfert/tree/main/.agents/skills/coding-standards into .agents/skills/coding-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coding-standards", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tiramisulabs/seyfert --skill coding-standards -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tiramisulabs/seyfert coding-standards --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tiramisulabs/seyfert.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/coding-standards .cursor/skills/coding-standards && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "coding-standards" agent skill from https://github.com/tiramisulabs/seyfert/tree/main/.agents/skills/coding-standards into .cursor/skills/coding-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coding-standards", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/tiramisulabs/seyfert.git --path .agents/skills/coding-standards--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add tiramisulabs/seyfert --skill coding-standards -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tiramisulabs/seyfert coding-standards --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tiramisulabs/seyfert.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/coding-standards .gemini/skills/coding-standards && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "coding-standards" agent skill from https://github.com/tiramisulabs/seyfert/tree/main/.agents/skills/coding-standards into .gemini/skills/coding-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coding-standards", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install tiramisulabs/seyfert coding-standardsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add tiramisulabs/seyfert --skill coding-standards -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/tiramisulabs/seyfert.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/coding-standards .github/skills/coding-standards && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "coding-standards" agent skill from https://github.com/tiramisulabs/seyfert/tree/main/.agents/skills/coding-standards into .github/skills/coding-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coding-standards", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tiramisulabs/seyfert --skill coding-standards -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install tiramisulabs/seyfert coding-standards --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tiramisulabs/seyfert.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/coding-standards .opencode/skills/coding-standards && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "coding-standards" agent skill from https://github.com/tiramisulabs/seyfert/tree/main/.agents/skills/coding-standards into .opencode/skills/coding-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coding-standards", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
coding-standards- GitHub stars
- 321
- Token cost
- ~1.1k tokens
- SKILL.md length
- 500 words
- Files
- 8 (incl. references)
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
Implement, fix, or refactor repository-native code, with attention to behavioral contracts, code shape, implementation economy, and meaningful verification.
- Tasks that involve Code quality
- SKILL.md covers Authority and scope, Choose the relevant guidance, Implementation criteria and Report
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Coding Standards is an agent skill from tiramisulabs/seyfert. Implement, fix, or refactor repository-native code, with attention to behavioral contracts, code shape, implementation economy, and meaningful verification. Use code-review-standards instead for read-only reviews of concrete changes.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including reference files (for example `agents/openai.yaml`, `references/behavioral-contracts.md` and `references/code-shape.md`).
It sits in Development, covering Code quality. It works with Discord. The repository describes itself as: the black magic Discord framework 🧙♂️. The licence is MIT.
When your agent uses it
- Tasks that involve Code quality
Example prompts
- “/coding-standards”
What it can do on your machine
Read from SKILL.md and the folder at commit b4b333e. 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.
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
Coding Standards loads about 1.1k tokens when it runs, and up to ~8.9k if it reads all its reference files. Until then it costs about 63 tokens; SKILL.md has 500 words of instructions outside code blocks.
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 tiramisulabs/seyfert at commit b4b333e, republished under its MIT licence (© tiramisulabs). 500 words, ~1,113 tokens.
Download SKILL.mdSave it as
.claude/skills/coding-standards/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.- name
- coding-standards
- description
- Implement, fix, or refactor repository-native code, with attention to behavioral contracts, code shape, implementation economy, and meaningful verification. Use code-review-standards instead for read-only reviews of concrete changes.
Coding Standards
Deliver the requested behavior with code that fits the repository, preserves supported contracts outside the requested change, and introduces only justified complexity.
Authority and scope
Follow the user's current instructions and existing authorization, then applicable repository instructions. Use effective configuration, executable contracts, and coherent source/caller/test patterns to establish behavior. Personal defaults and stored history are hints when stronger evidence is silent; they do not override the requested outcome.
Preserve dirty user work. Distinguish an explanation or review request from an implementation request. Continue authorized implementation through relevant verification and fixes; do not stop at the first draft or ask again for an already authorized action. Committing, pushing, publishing, deploying, and destructive cleanup require explicit authority for that action.
Treat intended behavior supported by types, documentation, tests, or callers as contract. Change it when the requested outcome authorizes that change. If a material contract decision remains unresolved, ask the smallest necessary question with the conflicting evidence and continue independent work. Resolve routine implementation choices from repository evidence. When a rule actually blocks progress, identify the exact instruction and explain why existing authorization does not resolve it.
Choose the relevant guidance
Read references when their decision applies, reusing context already established. A narrow edit does not require a repository-wide survey or every reference.
- Code shape: code-shape.md for variables, control flow, functions, types, and abstraction boundaries.
- Added complexity: implementation-economy.md when adding or reconsidering mechanisms, helpers, exports, or options.
- Runtime contracts: behavioral-contracts.md for errors, asynchronous work, concurrency, lifecycle, and public behavior.
- Repository conventions or ownership moves: repository-adaptation.md.
- Verification: implementation-verification.md when selecting checks or writing tests. A new test should reject a plausible wrong implementation, not merely assert that an edit exists.
- Self-review: quality-review.md for final correctness and quality assessment, including the representation-parity audit.
Show full SKILL.md (209 more words)Show less
Implementation criteria
Establish the observable outcome and relevant invariants from affected source and consumers. Make the smallest coherent root-cause change; reshape incidental structure when it obscures ownership, state, ordering, or failure semantics. Prefer repository-native constructs and existing owners over stylistic uniformity or speculative abstractions.
When responsibility crosses module, package, runtime, build, or deployment boundaries, account for the old owner's contracts with the ownership-transfer audit. When domain facts cross representations, account for semantic parity with the representation-parity audit. These are conditional correctness obligations, not optional substitutes for tests.
Implementation is complete when the requested behavior is implemented, the full patch has been reviewed, relevant checks support the changed contracts, and new failures within scope are resolved. Rerun affected checks after corrections. Broaden investigation or testing when risk, a failure, or an unresolved contract warrants it; stop once the evidence is sufficient and required checks pass. Report unavailable evidence without claiming the affected boundary is verified.
Report
Lead with the result and the evidence needed to assess it. Identify the meaningful behavior and files changed, relevant verification, and material limitations. Separate new failures, pre-existing failures, tooling defects, and unavailable checks. Keep routine reasoning and audit worksheets out of the response unless they help explain a decision or the user requests them.
© tiramisulabs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 7 other files (references) in .agents/skills/coding-standards of tiramisulabs/seyfert.
- SKILL.md
- agents/openai.yaml
- references/behavioral-contracts.md
- references/code-shape.md
- references/implementation-economy.md
- references/implementation-verification.md
- references/quality-review.md
- references/repository-adaptation.md
Open the folder on GitHubat commit b4b333e
Compare with similar skills
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Coding Standards this skilltiramisulabs/seyfert | 321 | — | ~1.1k | Automated safety check: Pass | MIT | |
| WooCommerce Code Reviewwoocommerce/woocommerce | 11k | 3 repos | ~1.1k | Automated safety check: Pass | Custom licence | |
| Systematic Code Refactoringluongnv89/claude-howto | 42k | — | ~3k | Automated safety check: Pass | MIT | |
| Install Anti-Slop Oxlint Rulesdmmulroy/anti-slop | 5.2k | — | ~2.2k | Automated safety check: Pass | MIT | |
| Constraint-Driven Developmentaddyosmani/agent-skills | 102k | 2 repos | ~5.2k | Automated safety check: Pass | MIT | |
| Skill Doli Code ReviewDolibarr/dolibarr | 7.7k | 1 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Systematic Code Refactoring
luongnv89/claude-howto
Guides refactoring in phases based on Martin Fowler's method: research, test coverage check, planning and small tested steps, with your approval at each phase.
Install Anti-Slop Oxlint Rules
dmmulroy/anti-slop
Installs, updates or migrates the vendored anti-slop Oxlint plugin in a repository, keeping local rule changes and the plugin's license and provenance files.
Constraint-Driven Development
addyosmani/agent-skills
Records a project's quality bar in CONSTRAINTS.md and watches diffs for signs an agent quietly weakened it, such as suppressions, skipped tests or lowered thresholds.
Skill Doli Code Review
Dolibarr/dolibarr
Reviews Dolibarr PHP code for compliance with coding standards and security best practices, and fixes identified issues.
Dignified Python Standards
docling-project/docling
Applies opinionated production Python conventions chosen by the project's Python version: modern type syntax, pathlib, explicit checks and interface guidance.
More from tiramisulabs/seyfert
Code Review Standards
tiramisulabs/seyfert
Review a concrete code change against an exact revision and produce evidence-backed findings.
Make No Mistakes
tiramisulabs/seyfert
Apply proportional rigor to high-risk implementation or operations involving public contracts, security, payments, data, production, migrations, or exhaustive scope.
Scope Discipline
tiramisulabs/seyfert
Prevent scope creep when a plan or implementation starts absorbing adjacent fixes, speculative compatibility work, migrations, or unrelated refactors.
Related
Works with
Categories
Questions about Coding Standards
What does Coding Standards do?
Implement, fix, or refactor repository-native code, with attention to behavioral contracts, code shape, implementation economy, and meaningful verification. Coding Standards is an agent skill from tiramisulabs/seyfert. Implement, fix, or refactor repository-native code, with attention to behavioral contracts, code shape, implementation economy, and meaningful verification.
When should I use Coding Standards?
Coding Standards fits situations like: tasks that involve Code quality.
How do I install Coding Standards in Claude Code?
Run `npx skills add tiramisulabs/seyfert --skill coding-standards -a claude-code`. Or copy the skill folder (.agents/skills/coding-standards in tiramisulabs/seyfert) into .claude/skills/coding-standards in your project. Claude Code loads it when a task matches its description.
How do I install Coding Standards in Codex?
Run `npx skills add tiramisulabs/seyfert --skill coding-standards -a codex`. Or copy the skill folder (.agents/skills/coding-standards in tiramisulabs/seyfert) into .agents/skills/coding-standards in your project. Codex loads it when a task matches its description.
Can I use 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 tiramisulabs/seyfert --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 Coding Standards need to run?
SKILL.md names no scripts, command-line tools or credentials: Coding Standards is instructions for the agent only.
Does 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 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 Coding Standards use?
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 Coding Standards use?
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 7.8k tokens, read only when the agent opens those files.
What are the alternatives to Coding Standards?
Skills that share tags, products or a category with Coding Standards: WooCommerce Code Review (woocommerce/woocommerce, 11k stars), Systematic Code Refactoring (luongnv89/claude-howto, 42k stars), Install Anti-Slop Oxlint Rules (dmmulroy/anti-slop, 5.2k stars) and Constraint-Driven Development (addyosmani/agent-skills, 102k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Coding Standards?
tiramisulabs (a GitHub organization) maintains it in tiramisulabs/seyfert, which has 321 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 7, 2026.
Source: tiramisulabs/seyfert on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.