SkillPartly tested (needs an account)

Clean up bolted-on feature code

make-native

After your assistant adds a feature, this skill rewrites the new code so it fits the existing design: no stray flags, copied files or special cases.

Works with
Claude Code, Codex CLI
Good for
Build an app, Web developers

What it does

When an AI assistant adds a new feature, it often takes the shortest path: an extra "if" here, a new flag there, or a copy of an existing file for the new case. Each change looks safe, but together they make the code harder to understand later.

make-native is a skill (a set of instructions your assistant reads) that cleans this up. It reads what the feature changed, studies the code around it and its history, and then rewrites the feature as if it had been planned from the start. It removes the workarounds, updates the tests to match and checks that nothing from the old version is left behind.

It is meant for new features only. The README says bug fixes should stay small, so do not use it on a bug-fix commit.

Example prompts

  • "Use make-native on this branch."

How to install

npx skills add Sloydai/make-native
git clone --depth 1 https://github.com/Sloydai/make-native.git /tmp/make-native
mkdir -p .claude/skills
cp -r /tmp/make-native/skills/make-native .claude/skills/

How to use it

When a feature is finished on a branch, ask: Use make-native on this branch. The assistant makes a separate refactor or feat commit so you can review the reshape on its own.

Check it works

The source gives no check command. After a manual install the file should be at .claude/skills/make-native/SKILL.md in your project (or ~/.claude/skills/make-native/ for all projects).

Common problems

Other assistants

  • Codex: copy the folder to .agents/skills/make-native/ (project) or ~/.agents/skills/make-native/ (all projects). The README also lists opencode, Kiro and GitHub Copilot folders — https://github.com/Sloydai/make-native

What to watch out for

  • Rewrites code across the files the feature touched, deletes or rewrites tests and makes its own git commit (no push); review that commit before you merge it
  • Can load by itself when a diff or branch adds a feature (no disable-model-invocation)
  • Tells the assistant to run git diff, git log -p, gh pr view and your project's build, linter and tests, so it runs commands in your project
  • The skill says the assistant may read runtime data such as logs, error tracking, analytics or database records if it has access (read only, never committed); limit what your assistant can reach
  • One Markdown file, no scripts. The manual install leaves a copy of the repo in /tmp/make-native. Young repo (created 2026-11-04, 0 forks); its only branch is add-make-native-skill, not main
  • npx skills add without -a asks which agents to install to; the skills CLI sends anonymous usage data unless DISABLE_TELEMETRY=1 or DO_NOT_TRACK=1 is set

Licence and author

Licence
MIT
Author
Sloydai
Source code
github.com/Sloydai/make-native

How we tested it

We installed it on an empty test computer on 9 Nov 2026. Partly tested: installed in a clean test system, but its main features need an account or key we did not use.

Test level

Not run on a real feature branch.

Technical details of the test
Date
9 Nov 2026
Method
Reviewed by our team at commit f7df61d: README and SKILL.md. In a clean test machine the README's manual lines (git clone, mkdir, cp) put SKILL.md in .claude/skills/make-native/, and npx skills add Sloydai/make-native -a claude-code -y did the same.

Checked again on 9 Nov 2026

Alternatives

  • code-simplifier — tidies recently changed code for clarity in general; make-native focuses on reshaping a new feature so it fits the original design

FAQ

  • Q: Will it change what my app does? A: It can. The skill uses a refactor commit when behaviour is unchanged and a feat commit when the reshape changes behaviour, so check which one it made.
  • Q: Do I need GitHub? A: No, but it uses the GitHub CLI (gh) to find a pull request's base branch if you have one.
  • Q: Does it run any scripts? A: No. It is one instruction file; the assistant runs git and your project's own tests.

Sources