opensrc-inspect
Opensrc Inspect
Use this skill when source-level dependency inspection is materially useful and API docs alone are not enough.
Workflow
- Read the repo
AGENTS.md. - Check existing snapshots first:
opensrc listcat opensrc/sources.jsonwhen present
- Prefer safe fetches that avoid repo mutation:
opensrc <package> --modify=falseopensrc pypi:<package> --modify=falseopensrc crates:<package> --modify=falseopensrc <owner>/<repo> --modify=false
- Inspect the fetched source path and cite exact files and versions when using it in analysis.
- 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
More from bjornmelin/dev-skills
streamdown
|
13zod-v4
Expert guidance for Zod v4 schema validation in TypeScript. Use when designing schemas, migrating from Zod 3, handling validation errors, generating JSON Schema/OpenAPI, using codecs/transforms, or integrating with React Hook Form, tRPC, Hono, or Next.js. Covers all Zod v4 APIs including top-level string formats, strictObject/looseObject, metadata, registries, branded types, and recursive schemas.
9vitest-dev
World-class Vitest QA/test engineer for TypeScript + Next.js (local + CI performance focused)
8docker-architect
SOTA Docker/Compose architecture, implementation, refactor, and security hardening. Use when working on containerization tasks such as creating or rewriting Dockerfiles, docker-compose files, buildx/bake configs, .dockerignore, and CI pipelines for build/test/scan/publish; auditing existing container setups for security, correctness, size/perf, and best practices (least privilege, non-root, minimal images, pinned base images, BuildKit secrets, healthchecks); debugging Docker build/run issues; or designing dev vs prod compose workflows across services (DB/cache/queues) with correct networking, volumes, secrets, and resource limits.
6notebook-ml-architect
>
5ai-sdk-ui
|
5