Opensrc Inspect
- 3 installs
- 5 repo stars
- Updated August 5, 2026
- bjornmelin/dev-skills
Opensrc-inspect is a Claude Code skill that fetches and inspects local opensrc source snapshots of packages and GitHub repos for source-level analysis.
About
Opensrc-inspect is a Claude Code skill for fetching, inspecting, and managing local opensrc source snapshots of packages and GitHub repositories. A developer uses it when API docs alone are not enough and source-level evidence is needed for a migration, bug, or compatibility question. It defaults to non-mutating --modify=false fetches and treats the opensrc/ directory as read-only source context.
- Fetches and manages local opensrc source snapshots for packages and GitHub repos
- Defaults to safe --modify=false fetches that avoid repo mutation
- Cites exact files and versions when source evidence is used in analysis
Opensrc Inspect by the numbers
- 3 all-time installs (skills.sh)
- Ranked #458 of 596 Debugging skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
opensrc-inspect capabilities & compatibility
Free; requires the opensrc CLI.
- Capabilities
- source inspection · dependency audit
- Works with
- github
- Use cases
- debugging · refactoring · research
- Pricing
- Free
What opensrc-inspect says it does
Fetch, inspect, and manage local opensrc source snapshots for packages and GitHub repositories.
You need source-level evidence for a migration, bug, or compatibility question.
Default to `--modify=false`.
npx skills add https://github.com/bjornmelin/dev-skills --skill opensrc-inspectAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 3 |
|---|---|
| repo stars | ★ 5 |
| Last updated | August 5, 2026 |
| Repository | bjornmelin/dev-skills ↗ |
What it does
Fetch and inspect a package or repo's local source snapshot for migration, bug, or compatibility analysis.
Who is it for?
Inspecting a package implementation and gathering source-level evidence for migrations, bugs, or compatibility questions.
Skip if: Cases where official docs, types, or direct code inspection already answer the question, or broad web research.
When should I use this skill?
Source-level dependency inspection is materially useful and API docs alone are not enough.
What you get
Fetched source target and version summary, exact local paths used, and whether deeper source inspection changed the conclusion.
- fetched source target and version summary
- exact local paths used for analysis
- recommendation on whether source inspection changed the conclusion
By the numbers
- 4 fetch spec forms (package, pypi, crates, owner/repo)
Files
Opensrc Inspect
Use this skill when source-level dependency inspection is materially useful and API docs alone are not enough.
Workflow
1. Read the repo AGENTS.md. 2. Check existing snapshots first:
opensrc listcat opensrc/sources.jsonwhen present
3. Prefer safe fetches that avoid repo mutation:
opensrc <package> --modify=falseopensrc pypi:<package> --modify=falseopensrc crates:<package> --modify=falseopensrc <owner>/<repo> --modify=false
4. Inspect the fetched source path and cite exact files and versions when using it in analysis. 5. Refresh snapshots after meaningful dependency upgrades if internals changed.
Use When
- You need to inspect a package implementation, not just its docs or types.
- You need source-level evidence for a migration, bug, or compatibility question.
Do Not Use When
- Official docs, types, or direct code inspection already answer the question.
- The task is broad web research or release-note discovery.
Guardrails
- Default to
--modify=false. - Treat
opensrc/as read-only source context. - Use Context7, Exa, or
web.runfor official/latest docs and changelogs; use opensrc only for implementation internals.
Outputs
- fetched source target and version summary
- exact local paths used for analysis
- concise recommendation on whether deeper source inspection changed the conclusion
interface:
display_name: "Opensrc Inspect"
short_description: "Fetch local source snapshots for package internals"
default_prompt: "Use $opensrc-inspect to inspect local opensrc snapshots or fetch a package/repo source safely with --modify=false before analyzing internals."
policy:
allow_implicit_invocation: false
Related skills
Azure DiagnosticsSystematically diagnose and resolve production issues on Microsoft Azure using official Microsoft guidance.495k1.3kAzure MessagingQuickly diagnose and fix connection, authentication, and message-processing failures when using Azure Event Hubs or Service Bus SDKs.483k1.3k
Diagnosing BugsGet a systematic, step-by-step process that surfaces the real root cause instead of guessing at bugs.291k200k
Use My BrowserWhen their agent task requires access to the live browser session, rendered DOM state, authenticated dashboards, localhost apps, or DevTools-selected elements instea269k71
Systematic DebuggingFollow a repeatable four-phase process that forces root-cause discovery before any code changes.210k265k
Safe DebugGet conservative, non-destructive diagnosis of deep learning and agent errors before any code changes are made.185k512FAQ
How does opensrc-inspect avoid mutating my repo?
It defaults to safe --modify=false fetches and treats the opensrc/ directory as read-only source context.
When should I refresh a snapshot?
Refresh snapshots after meaningful dependency upgrades if the internals changed.