Individual skill

rust-iterator-collections

Design and review Rust iterator pipelines and collection code for clear ownership, allocation, ordering, and error behavior. Use when writing, refactoring, or reviewing iterators, HashMap Entry usage, collect, FromIterator, Extend, custom iterators, or allocation-heavy loops.

plugins/LVTD-LLC/skills/skills/rust-iterator-collections/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,531
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Rust Iterator Collections

Use this skill to turn collection code into clear, idiomatic Rust. Prefer
iterator and collection APIs that express the operation directly while keeping
ownership, allocation, and error behavior visible.

## Core Workflow

1. Identify the input ownership mode: borrowed iteration, mutable iteration, or
   consuming iteration.
2. Pick the simplest iterator shape: `iter`, `iter_mut`, `into_iter`, ranges,
   `drain`, or a collection-specific method.
3. Replace manual loops with adapters only when the resulting code is clearer.
   Keep explicit loops for complex branching, early mutation, or debugging.