A project-infrastructure diagnosis command that checks testing, continuous integration, security basics, code-quality tools, documentation, and deployment readiness.

Use it to produce a report of critical, high, medium, low, and passed checks.

It identifies missing safeguards such as tests, input checks, secret protection, or automated checks, and groups them by urgency.

diagnose — Command for Claude Code by Vimalk0703/shipworthy

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/Vimalk0703/shipworthy

Made for: Claude Code.

Or install shipworthy, the plugin that ships this one along with the rest of its 66 skills, 7 commands, 3 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/vimalk0703/shipworthy/diagnose/github.svg)](https://agentmods.dev/commands/vimalk0703/shipworthy/diagnose)

Your own site

<a href="https://agentmods.dev/commands/vimalk0703/shipworthy/diagnose"><img src="https://agentmods.dev/badge/commands/vimalk0703/shipworthy/diagnose/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/vimalk0703/shipworthy/diagnose"><img src="https://agentmods.dev/badge/commands/vimalk0703/shipworthy/diagnose.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 560 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00560
Opus 5.5	$0.00000	$0.00224
Sonnet 5.5	$0.00000	$0.00112
Haiku 4.5	$0.00000	$0.00056

Measured 1mo ago against content hash 947d118adcb5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

diagnose scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/diagnose.md · 65 lines

How it starts

The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Before executing this command, output:

⚓ shipworthy › command: /diagnose — analyzing project infrastructure gaps

Run a full project infrastructure diagnosis.

Unlike /audit (which reviews code quality), this command checks what's missing entirely from the project.

Process

Run through the project-diagnosis skill checklist:
- Testing infrastructure (test directory, runner, coverage, actual tests)
- CI/CD configuration (workflows, test step, lint step)
- Security basics (.env in .gitignore, no hardcoded secrets, input validation, dependency audit)
- Code quality tools (linter, formatter, type checking)
- Architecture & documentation (architecture spec, README, .gitignore)
- Deployment readiness (health endpoint, structured logging, error tracking, env config)
Present findings organized by severity:
- Critical — fix immediately (security risks, secrets exposure)
- High — fix soon (no tests, no input validation)
- Medium — improve when convenient (no CI, no linter)
- Low — nice to have (no health endpoint, no .env.example)
- Passed — checks that passed (show as confirmation)
After presenting the report, ask the user:

"Want me to auto-fix what I can? I'll create missing configs and infrastructure files. I won't modify existing code without your approval."
If the user approves, dispatch the project-doctor agent (via subagent-driven-development) to fix the gaps.
After fixes, re-run the checklist and show before/after comparison.

Example Output

## Project Diagnosis Report

### Critical (fix immediately)
- [ ] .env not in .gitignore — secrets may be committed to git

### High (fix soon)
- [ ] No test files found — need tests/ directory and at least one test
- [ ] No input validation on API routes — install Zod and validate inputs

### Medium (improve when convenient)
- [ ] No CI configuration — need .github/workflows/ci.yml
- [ ] No linter — need ESLint with strict config

### Low (nice to have)
- [ ] No health endpoint for monitoring
- [ ] No .env.example documenting required environment variables

### Passed
- [x] .gitignore exists
- [x] README.md exists
- [x] TypeScript strict mode enabled
- [x] No hardcoded secrets detected
- [x] Dependencies have no critical vulnerabilities

---
Score: 5/12 checks passed
Want me to auto-fix what I can?

Read the full file on GitHub · 65 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 65 lines · 0 tokens per session scan A 947d118adcb5

Subscribe to this mod's changes

diagnose is a command published in the GitHub repository Vimalk0703/shipworthy (6 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 560 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code Debugging DevOps and cloud ai-assisted-development ai-code-review ai-coding ai-engineering anthropic

dare-bugfix-design

Diagnostica bug em projeto existente e planeja correção cirúrgica via Método DARE. Gera DARE/DESIGN-Bugfix-[Nome].md com causa raiz, riscos de regressão e plano de ação mínimo.

dewtech-technologies/dare-method · 0 tokens

dare-info

Mostra versão do CLI, caminhos relevantes e a integridade da instalação DARE no projeto atual.

dewtech-technologies/dare-method · 0 tokens

quick-fix

Implement→review subagent loop with no planning phase, for a fix whose cause is known and whose shape is obvious, however many files it touches. No spec, no worktree, no docs or signals at the end; one audit. Routes to /subagent-diagnose on an unknown cause and to /atomic-plan on an open approach or contract choice.

damusix/atomic-claude · 73 tokens

diagnose