can-i-help

# Can I Help: interest-routed contribution matching Turn repository state into contributor action. Collect project context, ask the developer what kind of contribution they want, map that interest to the strongest native signals, then return exact file/line recommendations with data-backed rationale and an executable first step. The invariant: no vague "look around `src/`". Every recommendation names a file and preferably a line, states why the target matters, explains the local code in 2 to 3 sentences, and gives the first command or edit. ## When to Apply / NOT Apply: - A contributor asks where to start, what needs work, or what would be a good first issue. - A maintainer wants to route a helper toward tests, bugs, docs, or cleanup using repo evidence. - An OSS project has open issues but unclear contribution paths. - The user wants quick, low-risk cleanup and accepts the verification gate before deletion claims. NOT: - The user already named the exact task or issue; solve that task instead. - The repo cannot be read locally and no public issue tracker is available; report the missing substrate. - The user asks for maintainer-only triage, release planning, or architectural roadmap work. - The request is pure project orientation with no contribution decision; produce orientation, not recommendations. ## Workflow 1. **Resolve target and collect base context.** Default target = current repo unless the user supplied a path. Capture the project shape before ranking anythi...