一键在 Manus 中运行任何 Skill

pith-review

星标95

分支11

更新时间2026年4月15日 06:37

One-shot structured code review. Use when reviewing a PR, diff, file, or function. Format: one line per issue. No summaries. Does not persist.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

abhisekjha

abhisekjha/pith

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Severity levels

BUG — incorrect behavior, will break in normal use
RISK — correct now but fragile, will break under specific conditions
SEC — security vulnerability (injection, auth bypass, data exposure, etc.)
PERF — measurable performance problem
NIT — style, naming, minor readability improvement
Q — genuine question about intent, not a criticism

Rules

One line per issue. Hard limit.
No preamble. No "Overall this looks good." No trailing summary.
If no issues: single line No issues found.
File prefix only when reviewing multiple files: auth.ts L42: BUG ...
Fix must be specific. Not "handle this better" — the actual change.
SEC issues: describe the attack vector, not just "this is insecure."

Examples

L42:  BUG  token.exp compared in wrong unit (seconds vs ms). Fix: token.exp * 1000 < Date.now()
L87:  SEC  /auth endpoint has no rate limiting — brute-force viable. Fix: add express-rate-limit, max 10/min per IP
L103: RISK db.query() not wrapped in try/catch — uncaught rejection crashes server. Fix: wrap, return 500
L118: NIT  variable named `data` — too generic. Fix: rename to `userProfile`
L201: Q    Why is this cached for 24h? Stale user data seems risky here.

For a file with no path given

Start each line with the line number only: L42: BUG ...

For multiple files

Prefix with filename: routes/auth.ts L42: BUG ...

One-shot. Does not persist.

同仓库更多 Skills

同仓库

pith-wiki

abhisekjha/pith

Wiki mode — persistent knowledge base maintenance. Active during /pith wiki mode. Defines page formats, ingest workflow, query workflow, and lint checks.

2026-04-1795

pith-setup

abhisekjha/pith

Pith onboarding conversation. Runs on first session in a new project. Introduces Pith, offers wiki setup, guides through initialization. Injected by session-start.js when no prior setup detected.

2026-04-1695

pith-graph

abhisekjha/pith

Run the Pith wiki graph generator for the current project. Scans wiki/ for .md files, extracts [[wikilinks]], and opens an interactive force-directed graph in the browser as wiki-graph.html.

2026-04-1695

pith-install

abhisekjha/pith

Install Pith into Claude Code. Copies hooks, patches settings.json, registers slash commands (/pith, /budget, /focus), and records the plugin root so hooks can resolve paths.

2026-04-1695

pith-tour

abhisekjha/pith

Interactive guided tour of Pith. Walks the user through each feature experientially — one step at a time, hands-on, using their actual project. Resumable. Skippable. State tracked via tour.py.

2026-04-1695

pith-uninstall

abhisekjha/pith

Uninstall Pith from Claude Code. Removes hooks, slash commands, and cleans pith entries from settings.json. Preserves ~/.pith/state.json (token history) unless user explicitly asks to wipe all data.

2026-04-1695

name	pith-review
description	One-shot structured code review. Use when reviewing a PR, diff, file, or function. Format: one line per issue. No summaries. Does not persist.

One line per issue. Exact format:

L<line>: <SEVERITY> <what is wrong>. Fix: <exact change>.

Severity levels

BUG — incorrect behavior, will break in normal use
RISK — correct now but fragile, will break under specific conditions
SEC — security vulnerability (injection, auth bypass, data exposure, etc.)
PERF — measurable performance problem
NIT — style, naming, minor readability improvement
Q — genuine question about intent, not a criticism

Rules

One line per issue. Hard limit.
No preamble. No "Overall this looks good." No trailing summary.
If no issues: single line No issues found.
File prefix only when reviewing multiple files: auth.ts L42: BUG ...
Fix must be specific. Not "handle this better" — the actual change.
SEC issues: describe the attack vector, not just "this is insecure."

Examples

L42:  BUG  token.exp compared in wrong unit (seconds vs ms). Fix: token.exp * 1000 < Date.now()
L87:  SEC  /auth endpoint has no rate limiting — brute-force viable. Fix: add express-rate-limit, max 10/min per IP
L103: RISK db.query() not wrapped in try/catch — uncaught rejection crashes server. Fix: wrap, return 500
L118: NIT  variable named `data` — too generic. Fix: rename to `userProfile`
L201: Q    Why is this cached for 24h? Stale user data seems risky here.

For a file with no path given

Start each line with the line number only: L42: BUG ...

For multiple files

Prefix with filename: routes/auth.ts L42: BUG ...

One-shot. Does not persist.