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.
A skill your agent uses when writing, fixing, editing, or refactoring TypeScript tests.
$ npx skills add ertugrul-dmr/clean-code-skills --skill clean-tests -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ertugrul-dmr/clean-code-skills clean-tests --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-tests .claude/skills/clean-tests && 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-tests" agent skill from https://github.com/ertugrul-dmr/clean-code-skills/tree/main/skills/typescript/clean-tests into .claude/skills/clean-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-tests", 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-testsType 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-tests -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ertugrul-dmr/clean-code-skills clean-tests --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-tests .agents/skills/clean-tests && 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-tests" agent skill from https://github.com/ertugrul-dmr/clean-code-skills/tree/main/skills/typescript/clean-tests into .agents/skills/clean-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-tests", 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-tests -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ertugrul-dmr/clean-code-skills clean-tests --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-tests .cursor/skills/clean-tests && 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-tests" agent skill from https://github.com/ertugrul-dmr/clean-code-skills/tree/main/skills/typescript/clean-tests into .cursor/skills/clean-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-tests", 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-tests--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-tests -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ertugrul-dmr/clean-code-skills clean-tests --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-tests .gemini/skills/clean-tests && 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-tests" agent skill from https://github.com/ertugrul-dmr/clean-code-skills/tree/main/skills/typescript/clean-tests into .gemini/skills/clean-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-tests", 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-testsInstalls 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-tests -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-tests .github/skills/clean-tests && 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-tests" agent skill from https://github.com/ertugrul-dmr/clean-code-skills/tree/main/skills/typescript/clean-tests into .github/skills/clean-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-tests", 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-tests -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-tests --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-tests .opencode/skills/clean-tests && 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-tests" agent skill from https://github.com/ertugrul-dmr/clean-code-skills/tree/main/skills/typescript/clean-tests into .opencode/skills/clean-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-tests", 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.
clean-testsA skill your agent uses when writing, fixing, editing, or refactoring TypeScript tests.
Clean Tests is an agent skill from ertugrul-dmr/clean-code-skills. Use when writing, fixing, editing, or refactoring TypeScript tests. Enforces Clean Code principles—fast tests, boundary coverage, one assert per test.
Its SKILL.md is about 1.4k 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 and Refactoring. It works with TypeScript. The licence is MIT.
Read from SKILL.md and the folder at commit 1b6b3cc. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
vitestFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Clean Tests loads about 1.4k tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 252 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.
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.
The full file from ertugrul-dmr/clean-code-skills at commit 1b6b3cc, republished under its MIT licence (© ertugrul-dmr). 252 words, ~1,387 tokens.
.claude/skills/clean-tests/SKILL.md (or your agent's skills folder).Test everything that could possibly break. Use coverage tools as a guide, not a goal.
// Bad - only tests happy path
test("divide", () => {
expect(divide(10, 2)).toBe(5);
});
// Good - tests edge cases too
test("divide normal", () => {
expect(divide(10, 2)).toBe(5);
});
test("divide by zero", () => {
expect(() => divide(10, 0)).toThrow(RangeError);
});
test("divide negative", () => {
expect(divide(-10, 2)).toBe(-5);
});Coverage tools report gaps in your testing strategy. Don't ignore them.
# Run with coverage
vitest run --coverage
# Aim for meaningful coverage, not 100%Trivial tests document behavior and catch regressions. They're worth more than their cost.
// Worth having - documents expected behavior
test("user default role", () => {
const user = new User("Alice");
expect(user.role).toBe("member");
});Don't use test.skip to hide problems. Either fix the test or delete it.
// Bad - hiding a problem
test.skip("async operation", () => {
// flaky, fix later
});
// Good - either fix it or document why it's skipped
test.skip("cache invalidation - requires Redis (see CONTRIBUTING.md)", () => {
});Bugs congregate at boundaries. Test them explicitly.
test("pagination boundaries", () => {
const items = Array.from({ length: 100 }, (_, i) => i);
// First page
expect(paginate(items, 1, 10)).toEqual(items.slice(0, 10));
// Last page
expect(paginate(items, 10, 10)).toEqual(items.slice(90, 100));
// Beyond last page
expect(paginate(items, 11, 10)).toEqual([]);
// Page zero (invalid)
expect(() => paginate(items, 0, 10)).toThrow(RangeError);
// Empty list
expect(paginate([], 1, 10)).toEqual([]);
});When you find a bug, write tests for all similar cases. Bugs cluster.
// Found bug: off-by-one in date calculation
// Now test ALL date boundaries
test("month boundaries", () => {
expect(lastDayOfMonth(2024, 1)).toBe(31); // January
expect(lastDayOfMonth(2024, 2)).toBe(29); // Leap year February
expect(lastDayOfMonth(2023, 2)).toBe(28); // Non-leap February
expect(lastDayOfMonth(2024, 4)).toBe(30); // 30-day month
expect(lastDayOfMonth(2024, 12)).toBe(31); // December
});When tests fail, look for patterns. They often point to deeper issues.
// If all async tests fail intermittently,
// the problem isn't the tests—it's the async handlingLook at which code paths are untested. Often they reveal design problems.
// If you can't easily test a function, it probably does too much
// Refactor for testabilitySlow tests don't get run. Keep unit tests under 100ms each.
// Bad - hits real database
test("user creation", async () => {
const db = await connectToDatabase(); // Slow!
const user = await db.createUser("Alice");
expect(user.name).toBe("Alice");
});
// Good - uses mock or in-memory
test("user creation", async () => {
const db = new InMemoryDatabase();
const user = await db.createUser("Alice");
expect(user.name).toBe("Alice");
});// Bad - testing multiple things
test("user", () => {
const user = new User("Alice", "alice@example.com");
expect(user.name).toBe("Alice");
expect(user.email).toBe("alice@example.com");
expect(user.isValid()).toBe(true);
user.activate();
expect(user.isActive).toBe(true);
});
// Good - one concept each
test("user stores name", () => {
const user = new User("Alice", "alice@example.com");
expect(user.name).toBe("Alice");
});
test("user stores email", () => {
const user = new User("Alice", "alice@example.com");
expect(user.email).toBe("alice@example.com");
});
test("new user is valid", () => {
const user = new User("Alice", "alice@example.com");
expect(user.isValid()).toBe(true);
});
test("user can be activated", () => {
const user = new User("Alice", "alice@example.com");
user.activate();
expect(user.isActive).toBe(true);
});| Rule | Principle |
|---|---|
| T1 | Test everything that could break |
| T2 | Use coverage tools |
| T3 | Don't skip trivial tests |
| T4 | Ignored test = ambiguity question |
| T5 | Test boundary conditions |
| T6 | Exhaustively test near bugs |
| T7 | Look for patterns in failures |
| T8 | Check coverage when debugging |
| T9 | Tests must be fast (<100ms) |
© 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
Just SKILL.md in skills/typescript/clean-tests of ertugrul-dmr/clean-code-skills.
Open the folder on GitHubat commit 1b6b3cc
Clean Tests 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 Tests this skillertugrul-dmr/clean-code-skills | 197 | — | ~1.4k | Automated safety check: Pass | MIT | |
| DRY Refactoring With jscpdkucherenko/jscpd | 6.4k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Qovery Console StandardsQovery/console | 227 | — | ~924 | Automated safety check: Pass | MIT | |
| jscpd Duplicate Code Detectorkucherenko/jscpd | 6.4k | — | ~4.5k | Automated safety check: Pass | MIT | |
| Coding Standardsmrzmyr/pixy-mood-tracker-app | 153 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Typescript Best Practicesjwynia/agent-skills | 170 | — | ~2.5k | Automated safety check: Pass | MIT |
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.
Qovery/console
Qovery Console coding standards, architecture guidelines, naming conventions, testing practices, and development workflows.
kucherenko/jscpd
Finds duplicated code in 220+ languages with jscpd, reports exact, renamed and near-miss clones in a compact agent-friendly format and measures duplication.
mrzmyr/pixy-mood-tracker-app
A skill your agent uses when writing, reviewing, or refactoring TypeScript
jwynia/agent-skills
Guide AI agents through TypeScript coding best practices including type safety, error handling, code organization, and architecture patterns.
LeoYeAI/openclaw-master-skills
Code review automation for TypeScript, JavaScript, Python, Go, Swift, Kotlin.
ertugrul-dmr/clean-code-skills
A skill your agent uses when fixing, editing, changing, debugging, or working with any Python code.
ertugrul-dmr/clean-code-skills
A skill your agent uses when fixing, editing, changing, debugging, or working with any TypeScript code.
ertugrul-dmr/clean-code-skills
A skill your agent uses when writing, fixing, editing, or reviewing Python code quality.
ertugrul-dmr/clean-code-skills
A skill your agent uses when writing, fixing, editing, or reviewing TypeScript code quality.
ertugrul-dmr/clean-code-skills
A skill your agent uses when naming, renaming, or fixing names of variables, functions, classes, or modules in Python.
ertugrul-dmr/clean-code-skills
A skill your agent uses when naming, renaming, or fixing names of variables, functions, classes, interfaces, or modules in TypeScript.
Works with
Categories
A skill your agent uses when writing, fixing, editing, or refactoring TypeScript tests. Clean Tests is an agent skill from ertugrul-dmr/clean-code-skills. Use when writing, fixing, editing, or refactoring TypeScript tests.
Clean Tests fits situations like: refactoring TypeScript tests; tasks that involve Code quality; tasks that involve Refactoring.
Run `npx skills add ertugrul-dmr/clean-code-skills --skill clean-tests -a claude-code`. Or copy the skill folder (skills/typescript/clean-tests in ertugrul-dmr/clean-code-skills) into .claude/skills/clean-tests in your project. Claude Code loads it when a task matches its description.
Run `npx skills add ertugrul-dmr/clean-code-skills --skill clean-tests -a codex`. Or copy the skill folder (skills/typescript/clean-tests in ertugrul-dmr/clean-code-skills) into .agents/skills/clean-tests in your project. Codex loads it when a task matches its description.
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-tests -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-tests, .gemini/skills/clean-tests, .github/skills/clean-tests and .opencode/skills/clean-tests in your project.
Going by SKILL.md and its folder, Clean Tests needs the command-line tools its instructions call (vitest).
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.
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.
Clean Tests is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Clean Tests: DRY Refactoring With jscpd (kucherenko/jscpd, 6.4k stars), Qovery Console Standards (Qovery/console, 227 stars), jscpd Duplicate Code Detector (kucherenko/jscpd, 6.4k stars) and Coding Standards (mrzmyr/pixy-mood-tracker-app, 153 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.