Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

trace-scan

Estrelas20

Forks4

Atualizado10 de julho de 2026 às 08:28

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. Trigger phrases: "scan traces", "trace scan", "AI trace", "check vendor name", "pre-commit audit"

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

byerlikaya

byerlikaya/claude-starter-kit

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	trace-scan
description	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. Trigger phrases: "scan traces", "trace scan", "AI trace", "check vendor name", "pre-commit audit"

Trace Scan (trace-scan)

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.

Mais deste repositório

mesmo repositório

eval-grader

byerlikaya/claude-starter-kit

Measure output quality, don't vibe it: score a generative task with a two-layer grader — deterministic code metrics + per-dimension LLM-as-judge — over a fixed task set, as signed deltas vs a pinned baseline. Grades cost alongside correctness (pass-slow). Trigger phrases: "eval", "grader", "measure output quality", "LLM-as-judge", "score the output"

2026-07-1920

frontend

byerlikaya/claude-starter-kit

Stack-agnostic frontend discipline (web · mobile · desktop): component structure, state, data fetching, loading/empty/error states, i18n, accessibility, performance. frontend-expert-csk applies it on every stack. Trigger phrases: "frontend", "screen", "component", "page", "UI", "state management", "interface"

2026-07-1920

iterate

byerlikaya/claude-starter-kit

Refine-to-Done loop: repeat until tests green + review clean + nothing deferred; bounded. Not the harness /loop. Trigger phrases: "iterate", "loop until done", "keep going until"

2026-07-1920

security-scan

byerlikaya/claude-starter-kit

Stack-agnostic security audit: map the attack surface, trace untrusted input to dangerous calls, surface dependency and configuration flaws. Severity-ranked report with fixes. Trigger phrases: "security scan", "run a security scan", "OWASP check", "scan for vulnerabilities", "find security vulnerabilities", "security audit"

2026-07-1920

threat-model

byerlikaya/claude-starter-kit

Scope a security audit BEFORE scanning, to cut false positives: map assets, entry points, trust boundaries and 5-8 domain-specific attack classes into a parseable THREAT_MODEL.md. A threat survives a patch; a vulnerability is only evidence for one. Feeds security-scan. Trigger phrases: "threat model", "attack surface", "scope the audit", "trust boundary"

2026-07-1920

sonarqube-check

byerlikaya/claude-starter-kit

SonarQube quality gate (language-agnostic, local-first): 0 Bugs/Vulns/Hotspots/Code Smells, 0 build warnings. If no analyzer exists, install the language's local server-less Sonar analyzer and run it — never a remote server. Trigger phrases: "sonarqube", "quality gate", "code smell", "sonar scan"

2026-07-1620

name	trace-scan
description	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. Trigger phrases: "scan traces", "trace scan", "AI trace", "check vendor name", "pre-commit audit"

Trace Scan (trace-scan)

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.