Skip to content
cccskills
FreePublished on GitHub

review-rust-prose

Review touched Rust files for prose-comment quality, rustdoc accuracy, and manually chopped comment wrapping. Use when a broad review needs a dedicated Rust prose/rustdoc pass or when the user asks for comment-quality review specifically.

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

See how to install

Files included (1)

  • SKILL.md2.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Review Rust Prose — Incan Compiler

Purpose

/review-rust-prose is a narrow report-only reviewer for touched .rs files that contain ///, //!, or prose //.

Own:

  • rustdoc paragraph shape
  • manually chopped comment wrapping
  • touched doc/comment accuracy against current behavior
  • public/non-trivial documentation coverage in touched Rust code

Do not own:

  • test style
  • docs-site markdown
  • architectural placement
  • final branch-clean judgment

Output artifact

Write a slice report at:

  • .agents/state/review-report.rust-prose.md

Do not write to the canonical .agents/state/review-report.md.

Workflow

  1. Review only the touched .rs files assigned by the orchestrator. If no slice was assigned, limit yourself to touched .rs files with prose comments.
  2. For each file, inspect touched prose blocks directly. Do not infer prose quality from broad code reading.
  3. Flag:
    • clause-by-clause or narrow-column manual wrapping
    • fake paragraph breaks
    • stale or misleading rustdoc
    • missing touched public/non-trivial docs that should exist
  4. Treat the accepted shape as:
    • natural paragraph prose, then make fmt wrapping
    • or multiple paragraphs separated for a real semantic break
  5. Record only Rust prose/documentation findings for this slice.

Slice report shape

Keep slice reports findings-first. Do not enumerate every clean file with a full checklist. Only record:

  • actual findings,
  • and, optionally, a short ## Reviewed Clean Surfaces section for risky or non-obvious clean calls.
# Review Slice Report

- role: rust-prose
- worker: <agent-id or stable label>
- status: in_progress | clean | blocked

## Scope
- assigned files:
  - src/foo.rs

## Findings

- [ ] warning | rustdoc prose | src/foo.rs:42
  Manually chopped single-paragraph rustdoc.

## Reviewed Clean Surfaces

- src/bar.rs — rust prose reviewed; no findings

Only include ## Reviewed Clean Surfaces when the clean call matters to the orchestrator, such as:

  • touched .rs files with prose comments,
  • files that are likely to be checked by another reviewer,
  • or surfaces involved in disagreement resolution.

If there are no findings, say so explicitly.

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

Add a new learning to the agent learnings file. Use when the user says /add-learning, asks to record a lesson, or when an implementation produced a reusable insight worth preserving for future agents.

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

encero-systems/incan66Updated Oct 22, 2026

Transition an Incan RFC from one status to the next. Use when the user asks to promote, advance, or finalize an RFC, or says /bump-rfc. Handles Draft → Planned, Planned → In Progress, and In Progress → Implemented transitions.

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

encero-systems/incan66Updated Oct 22, 2026

Safely close out completed Incan work after a PR is merged by verifying merge status, syncing the base branch, removing task-owned local worktrees/assets, deleting merged local/remote branches, pruning refs, and reporting dirty or ambiguous leftovers. Use when the user says /closeout, asks to clean up after a merged PR, or wants local RFC/issue branch/worktree cleanup.

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

encero-systems/incan66Updated Oct 22, 2026

Drafts a GitHub issue title and body using the target repository's issue templates under .github/ISSUE_TEMPLATE. Use when the user asks to create, draft, or file a GitHub issue, bug report, feature request, chore, documentation issue, or RFC proposal, or wants issue text that matches the repo's template.

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

encero-systems/incan66Updated Oct 22, 2026

Drafts implementation plans with TDD, documentation updates, and repository verification commands before coding. Use when the user asks for an implementation plan, /create-plan, or structured pre-implementation design for work in encero workspaces (e.g. Incan, IncQL).

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

encero-systems/incan66Updated Oct 22, 2026

Generate a PR description following the repository's pull request template. Use when the user asks to create, draft, or generate a PR description for a pull request. The skill automatically locates the PR template in the target repository and fills it in based on the git diff.

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

encero-systems/incan66Updated Oct 22, 2026

See all skills by encero-systems

Report a problem with this skill