Skip to content
cccskills
FreePublished on GitHub

cr

Review the branch with /code-review at high, then answer the findings with /code-review-response.

The English summary is being prepared. Showing the original description.

wado-lang/wado119 stars(GitHub 119 + cccskills 0)

Run score Not tested

See how to install

Files included (1)

  • SKILL.md485 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Code Review and Response

  1. Invoke the code-review skill with high, over origin/main...HEAD: once the branch is pushed its upstream diff is empty, and a stale local main pulls in merged work.
  2. Answer its findings with the code-review-response skill. With no findings, invoke /distill alone: the response would have ended with it.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Measure Wado's performance or the size of the Wasm it generates, and refresh the benchmark/ and wasm-size/ README files. Use for any benchmarking or size-measurement request, whichever benchmark it names.

The English summary is being prepared. Showing the original description.

wado-lang/wado119Updated Oct 26, 2026

Measure how long GitHub Actions jobs and steps took across past runs, and find the pull request that made CI slower. Use for any question about CI duration, a slow job, or when CI got slow.

The English summary is being prepared. Showing the original description.

wado-lang/wado119Updated Oct 26, 2026

How to answer code review feedback — a human reviewer, CodeRabbit, or any review bot. Verify the findings, report the classes they are instances of to the user before fixing, then fix the class rather than the sites named. Put design decisions to the user, then run /distill. Invoke when responding to review comments on a pull request, or to the findings of a /code-review run.

The English summary is being prepared. Showing the original description.

wado-lang/wado119Updated Oct 26, 2026

Investigate and improve code coverage for the wado-compiler crate. Use for any question about what the tests do and do not reach, dead code included.

The English summary is being prepared. Showing the original description.

wado-lang/wado119Updated Oct 26, 2026

Use rust-gdb to inspect variables and step through code without modifying it. Prefer it over print debugging for any investigation into what the compiler is actually doing (lldb is unavailable on Claude Code Web).

The English summary is being prepared. Showing the original description.

wado-lang/wado119Updated Oct 26, 2026

Cut the branch down to what the code cannot say: reuse what exists, remove duplication, dead code, and wasted work, turn invariants into asserts, and delete the comments the code already speaks. Run it after answering review feedback too — a fix written to satisfy a reviewer is the least distilled code on the branch.

The English summary is being prepared. Showing the original description.

wado-lang/wado119Updated Oct 26, 2026

See all skills by wado-lang

Report a problem with this skill