Use when you need to inspect repositories, scripts, package managers, frameworks, entrypoints, configuration, databases, and reproducible failures before edits.
How this skill is triggered — by the user, by Claude, or both
Slash command
/skillry-core-operations:01-repo-diagnosticsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Inspect a repository before any edit: package manager, scripts, framework, runtime, entrypoints, configuration, env shape, database markers, and the reproducible failure. The goal is to ground every repair or feature plan in real evidence from the actual files rather than assumptions — and to confirm exactly how to run, build, and test the project before changing a line of it. The review is rea...
Inspect a repository before any edit: package manager, scripts, framework, runtime, entrypoints, configuration, env shape, database markers, and the reproducible failure. The goal is to ground every repair or feature plan in real evidence from the actual files rather than assumptions — and to confirm exactly how to run, build, and test the project before changing a line of it. The review is read-only first and never echoes secret values.
codebase-cartography.pnpm-lock.yaml is pnpm, yarn.lock is yarn, package-lock.json is npm, bun.lockb is bun; for Python poetry.lock, uv.lock, Pipfile.lock, or requirements.txt; also Cargo.toml, go.mod, Gemfile.lock, composer.json. Multiple lockfiles is itself a red flag.package.json "scripts", Makefile, Taskfile, justfile) and note the real dev, build, test, lint, typecheck, and start entrypoints — record the exact command to run each.package.json main/module/exports/bin, src/index|main, app/, server.*, Docker CMD/ENTRYPOINT, and Procfile..env.example, .env*, or config (values redacted) and mark required versus optional.prisma/schema.prisma, drizzle.config.*, knexfile.*, migrations/, supabase/, docker-compose database services, and ORM dependencies.Package manager and runtime:
.nvmrc, .tool-versions, engines, or mise.toml.node_modules (or the language equivalent) is present, or the install step is identified.Scripts and entrypoints:
main, bin, server.*, Docker CMD).Framework and monorepo:
Config, env, and data:
.env with real values; no secrets in tracked config.dist/, .next/, out/) are checked for freshness against source.# --- layout / state ---
# layout + working-tree state
ls -la && git status --short 2>/dev/null | head
# --- package manager ---
# which lockfiles exist (ambiguity check)
ls pnpm-lock.yaml yarn.lock package-lock.json bun.lockb poetry.lock uv.lock 2>/dev/null
# scripts + manager hints
cat package.json | jq '{scripts, packageManager, engines, workspaces}' 2>/dev/null
# --- runtime pins ---
# installed runtime versions
node -v; npm -v; pnpm -v 2>/dev/null; python3 --version
# pinned versions to compare against
cat .nvmrc .tool-versions 2>/dev/null
# --- env shape ---
# env var NAMES only (never values)
grep -hoE '^[A-Z0-9_]+=' .env.example .env 2>/dev/null | sort -u
# committed .env with values present (red flag)
git ls-files '.env' '.env.*' 2>/dev/null
# --- database markers ---
# schema / migration / ORM markers
fd -t f 'schema.prisma|drizzle.config|knexfile' . 2>/dev/null
ls migrations supabase 2>/dev/null
# --- monorepo ---
# workspace markers and which package owns the task
rg -n 'workspaces|packages/' package.json pnpm-workspace.yaml turbo.json nx.json 2>/dev/null | head
# --- framework markers ---
# frontend framework config
fd -t f 'next.config|vite.config|nuxt.config|astro.config|svelte.config|angular.json' . | head
# backend framework markers
rg -n 'express|fastify|nestjs|manage.py|artisan|config/routes.rb' . 2>/dev/null | head
# --- build artifacts ---
# built output and whether it is newer or older than source
ls -la dist build .next out 2>/dev/null
# --- entrypoints ---
# package entry definitions and binaries
cat package.json | jq '{main, module, exports, bin}' 2>/dev/null
# Docker / Procfile entrypoints
rg -n 'CMD|ENTRYPOINT' Dockerfile* 2>/dev/null; cat Procfile 2>/dev/null
# --- reproduce the failure ---
# run the failing command verbatim and keep the exit code
<failing-command>; echo "exit=$?"
npm install in a pnpm repo rewrites the lockfile and corrupts the dependency tree — always read the lockfile first.dist/ or .next/ can mask the real source state — confirm freshness before relying on a built output..nvmrc but the shell is on Node 18 — many "works on my machine" failures trace here..env values into logs or a report leaks credentials; print key names only and redact values.pnpm build exists diverges from how the project is actually built and tested.npm test when the project uses pnpm test with a different script body, so the "failure" never reproduces and the real one is missed..next/ or dist/ and concluding the source is broken when the artifact simply predates the fix.Return: the package manager and version; the key scripts with the exact command to run each; the framework and runtime; the entrypoints; the env var names (required versus optional, values redacted); the database markers; the monorepo layout; and the reproduced failure (command plus error plus exit code). End with the smallest next safe command to make progress.
.env with real values as a secret-exposure finding, redacted.Done means the package manager, scripts, framework, entrypoints, env shape, and database markers are identified from evidence; the reported failure is reproduced with its exit code; secrets are redacted to names only; and the next safe step is named.
npx claudepluginhub fluxonlab/skillry --plugin skillry-core-operationsProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.