Skip to content
Skills Library
Programming · Review & audit

code-quality

/code-quality

Use when writing or reviewing code, comments, tests, or docs.

Repository
treg ↗
Licence
Apache-2.0
Last repository change
27.10.2026

Assessment and security

82/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability21 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content21 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Use when writing or reviewing code, comments, tests, or docs.

Original author description

Use when writing or reviewing code, comments, tests, or docs.

How it works

SKILL.md has no level-two headings · 19 lines, 150 words

SKILL.md preview
---
name: code-quality
description: Use when writing or reviewing code, comments, tests, or docs.
metadata:
  internal: true  # repo tooling: hidden from `npx skills add superdesigndev/treg`
---

# Code quality

1. **Enforce, don't instruct.** If a machine can check a rule, add the check.
   Apply these rules to code you change; fix old code in its own PR.

2. **Comments: none by default.** Keep one only for behavior we cannot change
   (vendor, platform, protocol) or a public contract. A reason worth keeping
   moves to a test, the docs, or the commit message.

3. **Tests must be able to fail.** Test behavior through the real entry point;
   if a test still passes with every dependency returning None, it is fake.
   Break the behavior, show the failing run, then land it. Never turn CI
   green by skipping, retrying, sleeping, or loosening an assertion.

4. **Docs say only what code cannot.** Keep a sentence only if, without it,
   the next person would change the code wrongly. Each fact once, where it
   belongs; when docs and code disagree, fix the doc.

Versions

RepositoryScoreLicence
This page · superdesigndev/treg82Apache-2.0
nasrulhazim/claude100MIT
piomin/claude-ai-spring-boot100Apache-2.0
joris887/exosuit100MIT
BlackBeltTechnology/pi-agent-dashboard100MIT
wrongstack/wrongstack100MIT
microsoft/winappcli100MIT
ingvarch/skills100MIT
oborchers/fractional-cto100MIT

Database snapshot: 13.11.2026 · package version a8afaba9c304 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100testing
    Applies repository-aware TDD, observable test design, and applicable quality checks. Use when changing behavior, writing tests, or reviewing test quality.
  • 90lantern-no-comments
    Use whenever writing, editing, or reviewing code and tempted to add a comment. Default to self-explanatory code — no comments that describe what a function/module/line does, no doc-blocks, no commented-out code. Comment ONLY for the non-obvious WHY: workarounds, gotchas,…
  • 100testing
    Apply comprehensive testing best practices including unit, integration, and e2e tests. Use when writing tests, reviewing test coverage, designing testable code, or setting up test infrastructure.
  • 100pg-prose-standard
    Use when writing, reviewing, restoring, trimming, or auditing prose in this repository, including deciding where documentation or comments are required across Markdown, JSDoc, code and test comments, descriptions, diagnostics, and CLI strings.
  • 100documentation-templates
    Structure templates for READMEs, API docs, code comments, changelogs and llms.txt. Use when writing or restructuring project documentation.
  • 100code-review
    Reviews a code change (diff, PR or pasted code) for design, correctness, complexity, tests, naming, comments, style and docs, with prioritized feedback. Use when the user asks to review code, a pull request, or wants feedback before merging.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.