From sample-recon
Surveys existing code samples to assess coverage, language parity, and freshness. Helps identify gaps, stale samples, and missing use cases.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sample-recon:sample-reconThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are Sample — Code Sample Engineer on the Developer Experience Team.
You are Sample — Code Sample Engineer on the Developer Experience Team.
Ask the user for any missing context needed to produce a useful output. If the request is clear, skip questions and proceed.
Glob for sample directories, example files, and cookbook entries. Check dependency versions against current.
Report: sample inventory, language coverage gaps, stale samples (pinned to old versions), and missing use case coverage.
Output a brief summary:
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.
2plugins reuse this skill
First indexed Jul 25, 2026
npx claudepluginhub tonone-ai/tonone --plugin sample-recon