Catch the accessibility failures that ship in almost every AI-built UI. Use after building any interactive component.
中文简介正在准备中。当前显示原文说明。
Archive228/loopkit7552026年7月15日 更新
免费在 GitHub 公开
owasp-review
Security-review a diff against the OWASP Top 10. Use before merging anything that touches auth, input handling, queries, or external calls.
中文简介正在准备中。当前显示原文说明。
查看安装方法包含的文件（1）
- SKILL.md1.0 KB
SKILL.md（原文）
安装前可以查看交给 AI 代理的指令内容。
OWASP Review
Check the diff for each, with the exact line:
- Injection — any string-built SQL/shell/HTML. Demand parameterized queries / escaping.
- Broken access control — does it verify the user OWNS the resource, not just that they're logged in?
- Auth — secrets in code? tokens without expiry? password compare not constant-time?
- SSRF — user-controlled URL fetched server-side without an allowlist.
- Sensitive data — PII/secrets logged, returned in errors, or sent unencrypted.
- Deserialization — untrusted input into pickle/yaml.load/eval.
- Dependency — a new package with known CVEs or no maintenance. Output: a list of {line, risk, fix}. If clean, say so explicitly. Never assume input is safe because "it comes from our frontend".
评价
还没有评价。欢迎分享你的使用感受。
评论
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
同一仓库的技能
Before compaction Loopkit extracts decisions into claude-decisions.json (machine-readable). Read it alongside claude-progress.txt at session start — prose is for humans, JSON is for the loop.
中文简介正在准备中。当前显示原文说明。
Archive228/loopkit7552026年7月15日 更新
Review a diff against the goal spec assuming the code is BROKEN. The reviewer that lives in the maker's head always agrees with itself — this pulls review into a hostile, separate pass. Invoke after every code change before marking work done.
中文简介正在准备中。当前显示原文说明。
Archive228/loopkit7552026年7月15日 更新
Verify that an endpoint checks ownership, not just authentication. Use on any handler that reads or mutates user data.
中文简介正在准备中。当前显示原文说明。
Archive228/loopkit7552026年7月15日 更新
Find the exact commit that introduced a bug. Use when something worked before and broke, and you don't know which change did it.
中文简介正在准备中。当前显示原文说明。
Archive228/loopkit7552026年7月15日 更新
Before picking new work, smoke-test the last "completed" feature. If it's broken, revert and re-open it before touching anything else. Kills the "looks shipped, isn't shipped" bug across sessions.
中文简介正在准备中。当前显示原文说明。
Archive228/loopkit7552026年7月15日 更新