跳到正文
cccskills
免费在 GitHub 公开

hostility-review

Audit an implementation against its plan with a hostile peer agent, debate findings to consensus, and drive fix waves until the auditor runs dry. Use when a done-claim needs verification the implementer cannot game ("hostile review", "adversarial audit", "is this PR faithful", "find the escape hatches") — the loop that beats the laziness bias with its own game theory.

中文简介正在准备中。当前显示原文说明。

juspay/kolu
查看安装方法

包含的文件（1）

  • SKILL.md2.3 KB

SKILL.md（原文）

安装前可以查看交给 AI 代理的指令内容。

Hostility review — done is the auditor's empty round

Reviews fail when author and auditor share an incentive: both want "done". This loop splits them. Five moves; the mechanics live in /kolu.

  1. Fresh hostile eyes, zero stake. The auditor is a different model that never saw the brief and doesn't answer for the outcome. It audits the diff against the PLAN — not the code against itself — seeded with the ledger of previously named cheats. Evidence discipline: every finding cites the code and quotes the plan sentence it violates. No vibes.

  2. Verify, then debate. Trust no finding and no rebuttal: check each against the code yourself, concede what's real, refute with evidence, loop to consensus per finding. Judgment forks go to the human; evidence disputes never do.

  3. Fix waves with predicates. Each consensus becomes a wave brief whose done-whens cannot be satisfied by their letter: greps that return nothing, mutations actually performed and observed red, type-level pins. A test seam never widens a public API. A claim without its executed check is a finding.

  4. Loop until dry. The implementer's "done" triggers a re-audit of the pushed delta — including fresh residue the fixes introduced, and whether a fix merely relocated the defect. The campaign ends only on the auditor's clean round.

  5. Ratchet and scope. Every named cheat joins the ledger (the next run starts smarter) and graduates, where possible, into a permanent check — yesterday's judgment is tomorrow's red build. The graduated check is the weakest predicate that still catches the named cheat — a broader one makes tomorrow's red build a false one (arXiv:2301.12987). Effort follows worth: framework surface, then production semantics, then app tests — a guard of a guard is rarely worth a wave.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护，适用 Google 的隐私权政策和服务条款。

同一仓库的技能

blog-post

免费

Write a kolu blog post grounded in the real build history — mine the Claude Code session logs behind a feature for the actual story (for large efforts, fan out over the transcripts with an ultracode workflow), draft it in the author's voice, and wire it into the Astro site. Use when asked to write a blog post or engineering essay about something that was built, especially one that should read as a narrative of what actually happened rather than invented marketing copy.

中文简介正在准备中。当前显示原文说明。

juspay/kolu822026年10月19日 更新

ci

免费

Run this repo's CI end-to-end — the kolu-specific procedure on top of the odu runner: the odu MCP front door, banned opt-out flags, linux-only platform pinning, venue-pool leasing, fail-fast surfacing, e2e timing evidence, and the green-gate. Triggers on "run CI", "drive CI", "re-run the pipeline", "close the red check", "warm the pool". Runner mechanics live in the `/odu` skill.

中文简介正在准备中。当前显示原文说明。

juspay/kolu822026年10月19日 更新

dev-server

免费

Launch the kolu dev server on two RANDOM free ports so it never collides with the running production `kolu.service`, remember the ports for the rest of the session, and tear down only the dev instance. Load before running the app locally — for evidence capture, driving a live kolu with the chrome-devtools MCP, or any `just dev` you'd otherwise run by hand. Triggers on "run kolu locally", "launch the dev server", "boot kolu", "drive a live kolu", "start the app to screenshot it", or before pointing chrome-devtools at a local kolu.

中文简介正在准备中。当前显示原文说明。

juspay/kolu822026年10月19日 更新

diataxis

免费

Classify, write, and audit documentation per Diátaxis (diataxis.fr) — the four-quadrant method (tutorials · how-to guides · reference · explanation). Encodes the compass as a decision procedure, each quadrant's contract as hard rules, and an executable mixed-mode audit. Project-agnostic; the per-repo doc-location mapping lives in a repo rule of the project's own (kolu: `.apm/instructions/diataxis.instructions.md`). Use when writing any user-facing doc, structuring a docs site, or auditing existing docs for mixed modes.

中文简介正在准备中。当前显示原文说明。

juspay/kolu822026年10月19日 更新

evidence

免费

Produce visual PR evidence — a screenshot or video — whenever a change has on-screen impact. Tests are never a substitute; a change can be backend by cause and visible by effect. Capture via the project's e2e harness on a pu box, or by driving a live kolu with the chrome-devtools MCP; host on a GitHub release and post a `## Evidence` comment. Triggers on "post evidence", "screenshot the change", "record a video of this", "show it working", "prove it", or finishing any change whose effect is visible on screen.

中文简介正在准备中。当前显示原文说明。

juspay/kolu822026年10月19日 更新

frontend-design

免费

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

中文简介正在准备中。当前显示原文说明。

juspay/kolu822026年10月19日 更新

查看 juspay 的全部技能

报告此技能的问题