Is Verify · Trojan0523 safe and trustworthy?

tashan scores Verify · Trojan0523 on public evidence — it is currently active, note: a single primary maintainer (bus-factor risk). Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Verify · Trojan0523?

Drop the skill folder into ~/.claude/skills/ (user scope) or .claude/skills/ (project scope).

Who maintains Verify · Trojan0523?

1 GitHub contributors, source: Trojan0523/sdd.

‹ The Index

Verify · Trojan0523

skill

【SDD 工作流】代码验证 + 迭代复盘：对 /sdd:exec 完成的改动执行质量门禁——git 状态检查 → 代码审查（走 reviewtarget adapter）→ 类型检查 → Lint → 测试（playground 复测或 testcmd）→ 迭代复盘（三层对话，产出 7-review.md）。失败触发 3 轮修复循环（禁止降低验收标准），产出 code-review-.md + test-report-.md 写入 plans/<ISSUE-ID/。触发条件：用户说 /sdd:verify、SDD 代码验证、SDD 迭代复盘时使用。

Works with: Claude Code (native) · Cursor, Codex CLI (manual)
native: this artifact type is that client's own format

Category: Dev Tools & CI — see all ranked ›

Install (Claude Code):

cp -r verify ~/.claude/skills/

Adoption: 6 repos
Upkeep: 48.0
Freshness: 64.0
Evidence coverage: 84% of the inputs this score can use — the rest are unknown, and the score is discounted for it
Health: active
Contributors: 1
License: MIT

Security audit

Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.

Its own instructions

Its SKILL.md shows worked examples.

Read from the capability’s own SKILL.md. This is not a grade and does not compare to the instruction-depth verdict on an MCP server — a skill has no tools to document, so that rubric does not apply to it.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

Pro adds the history to tashan doctor, so a run over your own config says which of yours gained an advisory, started running an install script, or lost its last maintainer — and what to move to.

The whole series behind any row, back to the first day we measured it
The replacement, named — not just the news that something died
tashan doctor over your own config, on your own machine

Start a 7-day trial › Everything measured on this page stays free.

source ↗ · skill:Trojan0523/verify

Everything on this page is public evidence and free. What it cannot know is whether you run this — check your whole config, free, in the browser. tashan Pro adds the series behind each row and names a replacement for anything dying.

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-09-13 · scorer s5 · how · something wrong here?