mirror of
https://github.com/phuryn/pm-skills.git
synced 2026-09-20 14:25:53 +03:00
Pawel HurynandClaude Opus 5
8607e3b077
Both sides added real content and this merge keeps both rather than picking one. The branch predates the v2.1.0 release, so merging it straight would have REVERTED that release: every plugin.json back from 2.1.0 to 2.0.0, and tests/test_consistency.py and tests/test_validator.py deleted. Merged instead of pushed. Conflicts, all resolved by combining: - pm-ai-shipping/.claude-plugin/plugin.json - v2.1.0's version, the branch's description. - security-audit-static - both checks survive as two steps: verify citations (2.1.0), then report with the OWASP Top 10 coverage backstop (branch). - ship-check - the new correctness review becomes Step 3, and 2.1.0's parallel security + performance pair renumbers to Steps 4 + 5 behind it, keeping the branch's model-mix carry-through on the security bullet. - Notes - 2.1.0's untrusted-input rule and both of the branch's bullets. The v2.1.0 test suite then caught what the branch had missed: a third skill in pm-ai-shipping without the counts to match. Root README headline 68 -> 69 skills, its pm-ai-shipping summary 2 -> 3, and marketplace.json's total and description synced to plugin.json. 15/15 tests and the validator pass. No version bump. The CHANGELOG entry sits under `## Unreleased`, which the tag-on-merge workflow ignores by design, so this lands the skill without cutting a release - that call is Pawel's. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01G42vsxSKL7je39AsHZ5aJm
36 lines
3.2 KiB
Markdown
36 lines
3.2 KiB
Markdown
# pm-ai-shipping — AI Shipping Kit
|
|
|
|
For PMs and founders accountable for AI-built code. Document a vibe-coded app, review it for correctness, security and performance defects, and produce a reviewer-ready shipping packet.
|
|
|
|
## Overview
|
|
|
|
AI agents write code fast but leave no record of *intent* — what the system should do, who may do what, where the secrets live. Without that record, no human and no auditing agent can tell whether the code is safe to ship. This kit restores reviewability: it documents the system, then audits the gap between what the docs say and what the code does — the class of bug generic scanners miss because they have no model of intent.
|
|
|
|
Start with `/ship-check` for the full sequence, or run a single stage with the specialist commands.
|
|
|
|
## Install
|
|
|
|
Install from the [pm-skills marketplace](https://github.com/phuryn/pm-skills) and enable the `pm-ai-shipping` plugin. Each command can be triggered with `/pm-ai-shipping:<command>` or its short `/<command>` form; skills auto-load when the topic matches.
|
|
|
|
## Skills (3)
|
|
|
|
- **shipping-artifacts** — The durable documentation set that makes an AI-built app reviewable: a core every app needs (architecture, user/permission flows, permissions, variables/secrets, test-coverage map) plus conditional docs added only when they apply (emails, cron, SEO, embedded agents/automation). Defines what each doc must capture and how a reviewer uses it.
|
|
- **code-review** — The top-level review skill. Correctness is its core; **performance and security are optional sub-cases** of the same engine. Anchors on agreements between participants across a boundary — the defects that are invisible file-by-file because each side looks reasonable alone — forces a violating execution, and refutes every candidate before reporting.
|
|
- **intended-vs-implemented** — The method for finding the gap between what a system is documented to do and what the code actually does, with cited evidence on both sides and without hand-wavy findings.
|
|
|
|
## Commands (5)
|
|
|
|
- `/pm-ai-shipping:ship-check` — Turn a vibe-coded repo into a reviewer-ready shipping packet: document, wire agent context, run correctness, security and performance reviews, add an independent unsteered pass by a second model, map test coverage, and compile the results.
|
|
- `/pm-ai-shipping:document-app` — Reverse-engineer a codebase into the system documents reviewers and auditors need — a core set (architecture, flows, permissions, variables) plus conditional docs (emails, cron, SEO, automation) when they apply.
|
|
- `/pm-ai-shipping:derive-tests` — Turn documented intent into a test-coverage map: inventory the tests that exist today, separate them from proposed tests and unverified gaps, mark each unit / guarded-live / manual, and recommend a green-before-merge CI gate.
|
|
- `/pm-ai-shipping:security-audit-static` — Static security audit: map trust boundaries, cross-reference documented intent, self-refute every finding, and report only evidence-backed risks.
|
|
- `/pm-ai-shipping:performance-audit-static` — Static performance audit: find N+1 queries and request waterfalls, over-fetching, missing indexes, and caching opportunities, ranked by effort and impact.
|
|
|
|
## Author
|
|
|
|
Paweł Huryn — [The Product Compass Newsletter](https://www.productcompass.pm)
|
|
|
|
## License
|
|
|
|
MIT
|