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.
A skill your agent uses when naming, renaming, or fixing names of variables, functions, classes, interfaces, or modules in TypeScript.
Install Clean Names
$ npx skills add ertugrul-dmr/clean-code-skills --skill clean-names -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ertugrul-dmr/clean-code-skills clean-names --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/ertugrul-dmr/clean-code-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/typescript/clean-names .claude/skills/clean-names && 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 "clean-names" agent skill from https://github.com/ertugrul-dmr/clean-code-skills/tree/main/skills/typescript/clean-names into .claude/skills/clean-names/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-names", 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/ertugrul-dmr/clean-code-skills/tree/main/skills/typescript/clean-namesType 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 ertugrul-dmr/clean-code-skills --skill clean-names -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ertugrul-dmr/clean-code-skills clean-names --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ertugrul-dmr/clean-code-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/typescript/clean-names .agents/skills/clean-names && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "clean-names" agent skill from https://github.com/ertugrul-dmr/clean-code-skills/tree/main/skills/typescript/clean-names into .agents/skills/clean-names/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-names", 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 ertugrul-dmr/clean-code-skills --skill clean-names -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ertugrul-dmr/clean-code-skills clean-names --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ertugrul-dmr/clean-code-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/typescript/clean-names .cursor/skills/clean-names && 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 "clean-names" agent skill from https://github.com/ertugrul-dmr/clean-code-skills/tree/main/skills/typescript/clean-names into .cursor/skills/clean-names/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-names", 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/ertugrul-dmr/clean-code-skills.git --path skills/typescript/clean-names--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 ertugrul-dmr/clean-code-skills --skill clean-names -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ertugrul-dmr/clean-code-skills clean-names --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ertugrul-dmr/clean-code-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/typescript/clean-names .gemini/skills/clean-names && 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 "clean-names" agent skill from https://github.com/ertugrul-dmr/clean-code-skills/tree/main/skills/typescript/clean-names into .gemini/skills/clean-names/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-names", 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 ertugrul-dmr/clean-code-skills clean-namesInstalls 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 ertugrul-dmr/clean-code-skills --skill clean-names -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ertugrul-dmr/clean-code-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/typescript/clean-names .github/skills/clean-names && 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 "clean-names" agent skill from https://github.com/ertugrul-dmr/clean-code-skills/tree/main/skills/typescript/clean-names into .github/skills/clean-names/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-names", 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 ertugrul-dmr/clean-code-skills --skill clean-names -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ertugrul-dmr/clean-code-skills clean-names --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ertugrul-dmr/clean-code-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/typescript/clean-names .opencode/skills/clean-names && 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 "clean-names" agent skill from https://github.com/ertugrul-dmr/clean-code-skills/tree/main/skills/typescript/clean-names into .opencode/skills/clean-names/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-names", 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
clean-names- GitHub stars
- 197
- Token cost
- ~1k tokens
- SKILL.md length
- 185 words
- Files
- 1
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when naming, renaming, or fixing names of variables, functions, classes, interfaces, or modules in TypeScript.
- Fixing names of variables
- SKILL.md covers N1: Choose Descriptive Names, N2: Choose Names at the…, N3: Use Standard Nomenclature… and N4: Unambiguous Names, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Modules in TypeScript
What it does
Clean Names is an agent skill from ertugrul-dmr/clean-code-skills. Use when naming, renaming, or fixing names of variables, functions, classes, interfaces, or modules in TypeScript. Enforces Clean Code principles—descriptive names, appropriate length, no encodings.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Code quality. It works with TypeScript. The licence is MIT.
When your agent uses it
- Fixing names of variables
- Modules in TypeScript
Example prompts
- “/clean-names”
What it can do on your machine
Read from SKILL.md and the folder at commit 1b6b3cc. 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
Clean Names loads about 1k tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 185 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 ertugrul-dmr/clean-code-skills at commit 1b6b3cc, republished under its MIT licence (© ertugrul-dmr). 185 words, ~1,039 tokens.
Download SKILL.mdSave it as
.claude/skills/clean-names/SKILL.md (or your agent's skills folder).- name
- clean-names
- description
- Use when naming, renaming, or fixing names of variables, functions, classes, interfaces, or modules in TypeScript. Enforces Clean Code principles—descriptive names, appropriate length, no encodings.
- when_to_use
- Also trigger on: single-letter or cryptic identifiers (`d`, `x`, `proc`), Hungarian notation (`strName`, `arrUsers`, `nCount`), `I`-prefixed interfaces…
Clean Names
N1: Choose Descriptive Names
Names should reveal intent. If a name requires a comment, it doesn't reveal its intent.
// Bad - what is d?
const d = 86400;
// Good - obvious meaning
const SECONDS_PER_DAY = 86400;
// Bad - what does this function do?
function proc(values: number[]) {
return values.filter((value) => value > 0);
}
// Good - intent is clear
function filterPositiveNumbers(numbers: number[]) {
return numbers.filter((number) => number > 0);
}N2: Choose Names at the Appropriate Level of Abstraction
Don't pick names that communicate implementation; choose names that reflect the level of abstraction of the class or function.
// Bad - too implementation-specific
function getMapOfUserIdsToNames() {
// ...
}
// Good - abstracts the data structure
function getUserDirectory() {
// ...
}N3: Use Standard Nomenclature Where Possible
Use terms from the domain, design patterns, or well-known conventions.
// Good - uses pattern name
class UserFactory {
create(data: unknown) {
// ...
}
}
// Good - uses domain term
function calculateAmortization(principal: number, rate: number, term: number) {
// ...
}N4: Unambiguous Names
Choose names that make the workings of a function or variable unambiguous.
// Bad - ambiguous
function rename(source: string, target: string) {
// ...
}
// Good - clear what's being renamed
function renameFile(oldPath: string, newPath: string) {
// ...
}N5: Use Longer Names for Longer Scopes
Short names are fine for tiny scopes. Longer scopes need longer, more descriptive names.
// Good - short name for tiny scope
const total = numbers.reduce((sum, n) => sum + n, 0);
// Good - longer name for module-level constant
const MAX_RETRY_ATTEMPTS_BEFORE_FAILURE = 5;
// Bad - short name at module level
const MAX = 5;N6: Avoid Encodings
Don't encode type or scope information into names. Modern editors make this unnecessary.
// Bad - Hungarian notation
const strName = "Alice";
const arrUsers: string[] = [];
const nCount = 0;
// Good - clean names
const name = "Alice";
const users: string[] = [];
const count = 0;
// Bad - interface prefix
interface IUserRepository {
findById(id: string): Promise<unknown>;
}
// Good - just name it
interface UserRepository {
findById(id: string): Promise<unknown>;
}N7: Names Should Describe Side Effects
If a function does something beyond what its name suggests, the name is misleading.
const configStore = new Map<string, string>();
// Bad - name doesn't mention file creation
function getConfig(configPath: string) {
if (!configStore.has(configPath)) {
configStore.set(configPath, "{}"); // Hidden side effect!
}
return JSON.parse(configStore.get(configPath) ?? "{}");
}
// Good - name reveals behavior
function getOrCreateConfig(configPath: string) {
if (!configStore.has(configPath)) {
configStore.set(configPath, "{}");
}
return JSON.parse(configStore.get(configPath) ?? "{}");
}Quick Reference
| Rule | Principle | Example |
|---|---|---|
| N1 | Descriptive names | SECONDS_PER_DAY not d |
| N2 | Right abstraction level | getUserDirectory() not getMapOf... |
| N3 | Standard nomenclature | UserFactory, calculateAmortization |
| N4 | Unambiguous | renameFile(oldPath, newPath) |
| N5 | Length matches scope | Short for loops, long for globals |
| N6 | No encodings | users not arrUsers |
| N7 | Describe side effects | getOrCreateConfig() |
© ertugrul-dmr, 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 skills/typescript/clean-names of ertugrul-dmr/clean-code-skills.
Open the folder on GitHubat commit 1b6b3cc
Compare with similar skills
Clean Names 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 |
|---|---|---|---|---|---|---|
| Clean Names this skillertugrul-dmr/clean-code-skills | 197 | — | ~1k | Automated safety check: Pass | MIT | |
| Install Anti-Slop Oxlint Rulesdmmulroy/anti-slop | 5.4k | — | ~2.2k | Automated safety check: Pass | MIT | |
| Code Reviewerjewbetcha/opentrace | 116 | 2 repos | ~1.1k | Automated safety check: Notes | MIT | |
| Coding Standardskurealnum/dotfiles | 290 | 17 repos | ~2.9k | Automated safety check: Pass | None | |
| Code Qualityredis/RedisInsight | 8.9k | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| Cross-Language Coding Standardszereight/gitlab-mcp | 2k | 1 repos | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
Code Reviewer
jewbetcha/opentrace
Comprehensive code review skill for TypeScript, JavaScript, Python, Swift, Kotlin, Go.
Coding Standards
kurealnum/dotfiles
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.
- Official
Code Quality
redis/RedisInsight
Code-quality standards for RedisInsight: TypeScript strictness, naming conventions (camelCase, PascalCase, UPPERSNAKECASE), linting rules, no any without reason, no !important in styles, and…
Cross-Language Coding Standards
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.
DRY Refactoring With jscpd
kucherenko/jscpd
Removes copy-paste duplication found by jscpd, starting with exact clones and hotspots, then renamed and near-miss copies, using proven refactoring strategies.
More from ertugrul-dmr/clean-code-skills
All 14 skills in this repoBoy Scout
ertugrul-dmr/clean-code-skills
A skill your agent uses when fixing, editing, changing, debugging, or working with any Python code.
Boy Scout
ertugrul-dmr/clean-code-skills
A skill your agent uses when fixing, editing, changing, debugging, or working with any TypeScript code.
Clean General
ertugrul-dmr/clean-code-skills
A skill your agent uses when writing, fixing, editing, or reviewing Python code quality.
Clean General
ertugrul-dmr/clean-code-skills
A skill your agent uses when writing, fixing, editing, or reviewing TypeScript code quality.
Clean Names
ertugrul-dmr/clean-code-skills
A skill your agent uses when naming, renaming, or fixing names of variables, functions, classes, or modules in Python.
Clean Tests
ertugrul-dmr/clean-code-skills
A skill your agent uses when writing, fixing, editing, or refactoring Python tests.
Related
Works with
Categories
Questions about Clean Names
What does Clean Names do?
A skill your agent uses when naming, renaming, or fixing names of variables, functions, classes, interfaces, or modules in TypeScript. Clean Names is an agent skill from ertugrul-dmr/clean-code-skills. Use when naming, renaming, or fixing names of variables, functions, classes, interfaces, or modules in TypeScript.
When should I use Clean Names?
Clean Names fits situations like: fixing names of variables; modules in TypeScript.
How do I install Clean Names in Claude Code?
Run `npx skills add ertugrul-dmr/clean-code-skills --skill clean-names -a claude-code`. Or copy the skill folder (skills/typescript/clean-names in ertugrul-dmr/clean-code-skills) into .claude/skills/clean-names in your project. Claude Code loads it when a task matches its description.
How do I install Clean Names in Codex?
Run `npx skills add ertugrul-dmr/clean-code-skills --skill clean-names -a codex`. Or copy the skill folder (skills/typescript/clean-names in ertugrul-dmr/clean-code-skills) into .agents/skills/clean-names in your project. Codex loads it when a task matches its description.
Can I use Clean Names 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 ertugrul-dmr/clean-code-skills --skill clean-names -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/clean-names, .gemini/skills/clean-names, .github/skills/clean-names and .opencode/skills/clean-names in your project.
What does Clean Names need to run?
SKILL.md names no scripts, command-line tools or credentials: Clean Names is instructions for the agent only.
Does Clean Names 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 Clean Names 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 Clean Names use?
Clean Names 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 Clean Names use?
About 1k tokens (SKILL.md is roughly 4.2k 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 Clean Names?
Skills that share tags, products or a category with Clean Names: Install Anti-Slop Oxlint Rules (dmmulroy/anti-slop, 5.4k stars), Code Reviewer (jewbetcha/opentrace, 116 stars), Coding Standards (kurealnum/dotfiles, 290 stars) and Code Quality (redis/RedisInsight, 8.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Clean Names?
ertugrul-dmr (a GitHub user) maintains it in ertugrul-dmr/clean-code-skills, which has 197 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on April 21, 2026.
Source: ertugrul-dmr/clean-code-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.