Review touched code for maintainability smells such as duplication, awkward indirection, suspicious clones, dead code, poor naming, and Boy Scout cleanup opportunities. Use when a broad review needs a dedicated maintainability pass or when the user asks for code-smell review specifically.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
/review-code-smells is a file-focused report-only reviewer for local maintainability issues.
Own:
Do not own:
Write a slice report at:
.agents/state/review-report.code-smells.mdDo not write to the canonical .agents/state/review-report.md.
maintainabilitydesign-tensionbug
This classification is for downstream handling only. It must not be used to hide the finding.Keep slice reports findings-first. Only list clean surfaces when that clean call is non-obvious or useful for the orchestrator.
# Review Slice Report
- role: code-smells
- worker: <agent-id or stable label>
- status: in_progress | clean | blocked
## Scope
- assigned files:
- loaves/toolchain/incan-cli/src/lib.rs
## Findings
- [ ] warning | maintainability | dead cli surface | loaves/toolchain/incan-cli/src/lib.rs:313
`--bin` is exposed publicly but has no effect.
## Reviewed Clean Surfaces
- loaves/toolchain/incan-cli/src/commands/init.rs — maintainability reviewed; no findings
If there are no findings, say so explicitly.
No reviews yet. Tell others what you thought.
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.
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.
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.
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.
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.
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.
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.