ediiloupatty

Declaude — AI skill for Claude Code

AI community

Remove Claude/AI attribution from a GitHub repo in one command clean commit history, force-push, and refresh the Contributors graph so @claude disappears.

How to install Declaude

This entry records only its repository, not the path inside it, so there is no exact command to give. Open ediiloupatty/declaude and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Declaude does

Remove Claude/AI attribution from a GitHub repo in one command clean commit history, force-push, and refresh the Contributors graph so @claude disappears.

Alternatives in AI

Humanizer: Remove AI Writing Patterns — You are a writing editor that identifies and removes signs of AI-generated text to make writing sound more nat 10.5k ★
Rb Setup — First-time setup 1.3k ★
Oil UI — Push AI UI design to its limits: explore distinct directions, compare them side by side, and refine against re 861 ★

README

declaude

**Remove Claude/AI attribution from a GitHub repo in one command.**

declaude OWNER/REPO

It clones the repo, strips Claude/AI traces from your **entire commit history** (e.g. `Co-Authored-By: Claude ` or _"Generated with Claude Code"_), force-pushes the cleaned branches, and **refreshes GitHub's Contributors graph** so `@claude` actually disappears — all without touching your code or your commit authorship.

Video

Why `@claude` won't go away by itself

AI tools append a `Co-Authored-By: Claude …` trailer to commits, and GitHub's **Insights → Contributors graph** counts those co-authors. That graph is a **cached, background-computed view** — a force-push (or a flush, or a commit) *on its own* doesn't reliably update it, so `@claude` lingers even after the history and the REST API are clean.

What actually works is a specific **order**:

**remove Claude → flush (rename the default branch) → push a fresh commit**

The flush resets GitHub's cached graph; the following commit triggers a recompute against the now-clean history. `declaude` does all three for you (the refresh commit is `chore: refresh GitHub contributors`, reusing your latest commit's author so no new identity appears). It runs **even when the history is already clean**, which is exactly what a previously-cleaned repo needs.

Timing matters too. GitHub serves its old commit index for a little while after a force-push, and flushing against that stale index just rebuilds the graph from the *old* history — putting `@claude` right back. So `declaude` waits until GitHub itself reports the history as clean before flushing, then **verifies the rebuilt graph** and repeats the flush → refresh if `@claude` survived. That's why one run is enough; you don't have to run it twice.