Code Review

Automated code review and analysis

Showing 241-264 of 8780 skills
melodic-software

Do your research — deep

by melodic-software

"Escalate research discipline to a heavy verification fan-out over a TYPED FULL INVENTORY of the session's claims — assumptions, asserted facts, concrete specifics (paths, defaults, flags, signatures), and load-bearing premises — verifying each against a primary source at a configurable depth (tiered by default, or full), then report a per-item ledger with verdict, source, source tier, consensus count, and recency. Use when: 'deep research pass', 'verify every claim', 'audit all our claims', 'fact-check everything', 'fact-check all these claims', 'go make sure those are all right', 'we've made a lot of load-bearing claims', or when your own judgement is the suspected bias across many claims. For a single or small inline fact-check ('fact-check that'), use the sibling do-your-research."

Academic 12 29d ago
melodic-software

Do your research

by melodic-software

"Re-anchor research and no-assumptions discipline mid-session, then self-audit and correct the current work. Use when: 'do your research', 'you're guessing', 'cite that', 'stop assuming', 'evidence, not vibes', 'you skipped verification', 'that's training-data recall', 'research this properly', 'fact-check', 'fact check this', 'make sure that's right', or at conversation start to set the posture. For a heavy verification fan-out — a typed full inventory of the session's claims verified at a configurable depth — use the sibling do-your-research-deep."

Code Review 12 23d ago
melodic-software

claude-code-plugins

by melodic-software

"Audit a codebase for drift between docs, config, code, and architecture. Verifies every factual claim against reality via parallel subagent fan-out, severity-rates findings and reports read-only; remediation is delegated to the implementation/verification lanes (--fix hands the findings to /implementation:implement then /verification:confirm). Use when: 'audit codebase', 'check for drift', 'verify docs', 'full audit'. Flags: --fix (hand findings to the remediation lanes after reporting), --docs-only, --code-only, --config-only, --arch-only."

Code Review 12 29d ago
melodic-software

Memory Health

by melodic-software

"Audit the Claude Code instruction/memory layer — CLAUDE.md, CLAUDE.local.md, .claude/rules/, and auto-memory — against a codified checklist derived from official Claude Code documentation. Use when: 'audit CLAUDE.md', 'memory health', 'audit rules', 'is my CLAUDE.md too long', 'prune instructions', after CLAUDE.md/rules changes or a Claude Code upgrade; actions: audit (default), fix, update, report."

CLI Tools 12 23d ago
melodic-software

claude-code-plugins

by melodic-software

"Verify the disk-hygiene plugin's runtime prerequisites and platform posture for this machine. Use when: 'set up disk-hygiene', 'configure disk-hygiene', 'is disk-hygiene working', a clean run reported a missing prerequisite, or before a first audit on a new machine. Actions: check (read-only verification, default) apply (resolve what check found). Re-runnable and safe."

CLI Tools 12 24d ago
melodic-software

Reuse or replace

by melodic-software

"Re-anchor the anti-fragmentation discipline that when an established way of doing something already exists — an idiom, structure, naming shape, doc format, or process — new work REUSES it or openly REPLACES it (migrate the old uses, record the decision); never a silent second, parallel way alongside. Then audit the work in flight for unexplained divergence from an established way. Replacing is first-class when evidence backs it — the sin is the SILENT second way, not divergence itself. Use when: 'reuse or replace', 'we already have a way of doing this', 'don't invent a second way', 'keep it one way', 'follow the existing pattern or replace it', 'be consistent', 'you added a parallel way', 'this diverges from how we do it elsewhere', or at conversation start on work that extends an established codebase, structure, or process."

Code Review 12 23d ago
melodic-software

Follow our standards

by melodic-software

"Re-anchor to your organization's engineering standards, then audit the work in flight against them and correct violations with doc citations. Use when: 'follow our standards', 'follow the standards', 're-anchor to standards', 'does this match our conventions', 'audit against standards', 'you're drifting from our conventions', or at conversation start on a repo governed by shared conventions."

Code Review 12 29d ago
melodic-software

Stateless

by melodic-software

"Inspect and turn off Claude Code's auto memory — the notes Claude writes itself per repo under ~/.claude/projects/<project>/memory/. Use when: 'make Claude stateless', 'stop Claude remembering', 'disable auto memory', 'turn off auto-memory', 'purge/clear/delete auto memory', 'wipe what Claude saved about this repo', 'does Claude have saved memories'. Actions: status (default — memory + settings across all scopes), disable (autoMemoryEnabled:false + CLAUDE_CODE_DISABLE_AUTO_MEMORY), purge (destructive delete, confirm-gated). Auto-memory only — not CLAUDE.md/rules (use /claude-memory:audit) and not transcripts/history."

CLI Tools 12 29d ago
melodic-software

Mind your maxims

by melodic-software

"Re-anchor cooperative-communication discipline — Grice's conversational maxims plus the AI-augmented transparency maxim — then audit recent responses and agent-authored artifacts for what the reader actually needed: completeness in both directions, relevance, clarity, and disclosed boundaries. Use when: 'mind your maxims', 'communication quality', 'answer what I asked', 'you buried the answer', 'you didn't answer the question', 'too vague', 'stay on topic', 'is this clear', 'grice', 'maxims', or at conversation start to set the communication posture."

Academic 12 29d ago
melodic-software

Reason, don't recite

by melodic-software

"Re-anchor the discipline that inherited content is evidence of what is, never self-justifying authority — then audit the work in flight for decisions coasting on precedent and re-derive them from first principles. Use when: 'reason don't recite', 'why is it this way', 'challenge that convention', 'you're deferring to precedent', \"that's just how it's done\", 'question the inherited design', 'stop reciting the docs', 'is this actually right', or at conversation start on legacy or inherited code."

Automation 12 23d ago
xiaowu89

image-audit

by xiaowu89

对图片进行鉴黄、政治、暴恐内容审核。先将图片压缩到 500px/JPEG 后直传 NX API 审核,以表格汇总结果。适用于用户提到图片审核、内容检查、鉴黄、政治识别、暴恐识别、违规扫描、图片安全、JPG/PNG/WebP 审核的场景。

API Dev 12 1mo ago
AuroraProudmoore

java-audit-skill

by AuroraProudmoore

AI驱动的Java/前端代码安全审计技能,实现系统化、高覆盖率的漏洞挖掘。使用场景: (1) 审计Java/Kotlin项目寻找安全漏洞(0day挖掘、代码审计、安全评估) (2) 审计前端项目(JavaScript/TypeScript/React/Vue)寻找安全漏洞 (3) 企业级代码库的安全审计(支持大型项目) (4) 需要高质量、低幻觉率的安全审计报告 (5) CI/CD集成的前期漏洞发现 触发关键词:Java审计、代码审计、安全审计、漏洞挖掘、0day、安全评估、前端审计、React审计、Vue审计、Java security audit、code review for security

Code Review 24 5mo ago
SiinXu

stock_analyzer

by SiinXu

"分析股票和市场。当用户想要分析单个或多个股票,或进行市场复盘时调用。"

Analytics 2 4mo ago
SiinXu

handle-review-feedback

by SiinXu

Process external review feedback on your own open PR by converging the full business contract instead of stacking point patches.

Code Review 2 26d ago
vercel

logs

by vercel

View Vercel deployment logs. Use when the user says "show logs", "check logs", "vercel logs", or "what went wrong with the deployment".

Automation 13 8mo ago
moido1092

algo-sensei

by moido1092

Your personal DSA & LeetCode mentor. Use for problem explanations, progressive hints, code reviews, mock interviews, pattern recognition, complexity analysis, and custom problem generation. Automatically adapts to your learning style and request type.

Code Gen 1 10mo ago
tuist

tuist-swift-review

by tuist

Project-specific pull request review rules for the tuist/tuist Swift codebases. Focuses on the things only this repo knows, including preferring value types, the testing framework choice, and migration of XCTest to Swift Testing.

Code Review 5.8K 2mo ago
costiash

docs

by costiash

Router for the /docs command. Look up Claude documentation, ask plain-English questions, generate interactive courses and HTML changelog reports, check freshness, and sync the local cache. Dispatches to the claude-docs, claude-docs-validate, claude-docs-course, and claude-docs-changelog skills.

Code Gen 49 1mo ago
ZhuLinsen

Analyze PR

by ZhuLinsen

关闭 PR

Code Review 64.5K 2mo ago
paperclipai

wiki-lint

by paperclipai

Use when an LLM Wiki operation issue is a lint or health check. Audit for contradictions, orphans, weak provenance, broken links, missing concept pages, and index/log drift; return triage findings without auto-fixing.

Code Review 80.1K 1mo ago
kenryu42

ccsn-find-simplifications

by kenryu42

'Use when working in the cc-safety-net repo to find non-obvious simplification candidates: dead, duplicated, speculative, over-built, or contract-exceeding surfaces in the analyzer, rules, guards, integrations, CLI, or GUI. Produces evidence-backed proposals for the maintainer, not a pile of guesses.'

Code Review 1.5K 20d ago
paperclipai

paperclip

by paperclipai

Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.

Code Review 80.1K 1mo ago
ZhuLinsen

daily-stock-analysis

by ZhuLinsen

调用 daily_stock_analysis API 做股票分析。当用户说「分析茅台」「analyze AAPL」「帮我看看 600519」或要大盘复盘时使用。优先用股票代码。

API Dev 64.5K 19d ago
tuist

compare-test-case

by tuist

Compares a single test case's behavior across two branches, analyzing pass/fail status, duration, flakiness, and failure details. Useful for investigating test regressions introduced by a feature branch.

Code Review 5.8K 5mo ago