How do I install the Trace Scan skill?

Run npx skillmds@latest add byerlikaya/trace-scan in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Trace Scan safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Trace Scan?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Trace Scan free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Trace Scan?

byerlikaya (@byerlikaya) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Trace Scan by byerlikaya — Agent Skill

Name: Trace Scan
Author: byerlikaya

File contents

Trace Scan (trace-scan)

Trigger phrases: "scan traces", "trace scan", "AI trace", "check vendor name", "pre-commit audit"

Purpose: to bind §4.1/§4.2 to a gate rather than to memory. If the rule lives only in text, a trace leaks sooner or later; this skill + the hooks stop the leak at commit time.

When

Before every commit (automatic: pre-commit + commit-msg hooks).
Before commit-agent-csk proposes a message (manual verification).

How

Pattern list: ./.claude/hooks/trace-blocklist.txt (grep -iE, one pattern per line).

Defaults are high-hit: co-author trailers, auto-generation footers, robot emoji, and AI-assistant/tool brand names. Standalone words that occur too often (model/assistant) are DELIBERATELY excluded. See trace-blocklist.txt for the exact list.
Vendor name is project-specific: ADD the name of the third-party template in use to the list (§4.2).

Manual scan (a quick look without the hook):

git diff --cached --unified=0 | grep -E '^\+' | grep -Ev '^\+\+\+' \
  | grep -iEf .claude/hooks/trace-blocklist.txt

Hook setup

start.sh sets git config core.hooksPath .claude/hooks (if there is a git repo). The hooks live under .claude → they are in gitignore and stay local (§4.3). To do it later for a repo:

git config core.hooksPath .claude/hooks
chmod +x .claude/hooks/pre-commit .claude/hooks/commit-msg

Rules

If there is a finding, the commit STOPS; the phrase is removed and the real rationale is written in human Turkish.
Skipping with --no-verify only on an EXPLICIT request (§4.5); the hook is not skipped silently.
On a false positive, narrow/remove the pattern — the list is set up by the project owner.

---name: trace-scandescription: Trace scan (§4.1/§4.2): before a commit, scans the staged changes and the message for AI traces (co-author trailers, footers, robot emoji, tool names) and vendor template names. The git hooks apply it automatically.---# Trace Scan (trace-scan)Trigger phrases: "scan traces", "trace scan", "AI trace", "check vendor name", "pre-commit audit"Purpose: to bind §4.1/§4.2 to a *gate* rather than to *memory*. If the rule lives only in text,a trace leaks sooner or later; this skill + the hooks stop the leak at commit time.## When- Before every commit (automatic: `pre-commit` + `commit-msg` hooks).- Before commit-agent-csk proposes a message (manual verification).## HowPattern list: `./.claude/hooks/trace-blocklist.txt` (grep -iE, one pattern per line).- **Defaults are high-hit:** co-author trailers, auto-generation footers, robot emoji, and AI-assistant/tool brand names. Standalone words that occur too often (model/assistant) are DELIBERATELY excluded. See trace-blocklist.txt for the exact list.- **Vendor name is project-specific:** ADD the name of the third-party template in use to the list (§4.2).Manual scan (a quick look without the hook):```bashgit diff --cached --unified=0 | grep -E '^\+' | grep -Ev '^\+\+\+' \ | grep -iEf .claude/hooks/trace-blocklist.txt```## Hook setup`start.sh` sets `git config core.hooksPath .claude/hooks` (if there is a git repo). The hooks liveunder `.claude` → they are in gitignore and stay local (§4.3). To do it later for a repo:```bashgit config core.hooksPath .claude/hookschmod +x .claude/hooks/pre-commit .claude/hooks/commit-msg```## Rules- If there is a finding, the commit STOPS; the phrase is removed and the real rationale is written in human Turkish.- Skipping with `--no-verify` only on an EXPLICIT request (§4.5); the hook is not skipped silently.- On a false positive, narrow/remove the pattern — the list is set up by the project owner.

Frequently asked questions

Trace Scan