19 lines
1.4 KiB
Markdown
19 lines
1.4 KiB
Markdown
---
|
|
name: repo-inspection-review
|
|
description: "Review repository inspection summaries for architecture, production readiness, and prioritized fixes using cited evidence. Use after deterministic GitHub file classification and risk scanning are complete."
|
|
---
|
|
# repo-inspection-review
|
|
|
|
# Repository Inspection Review
|
|
|
|
When reviewing a repository inspection summary:
|
|
|
|
1. Preserve exact citations from the deterministic scanner. Never invent files, line numbers, vulnerabilities, dependencies, or source snippets.
|
|
2. Summarize architecture from observed files only: tech stack, entrypoints, modules/services, data stores, integrations, deployment model, CI/CD flow, runtime/configuration model, and likely request/data flow.
|
|
3. Score production readiness conservatively. Security, dependency hygiene, test coverage, CI/CD, observability, configuration, deployment, docs, reliability, maintainability, and CI/CD should all be grounded in evidence.
|
|
4. Prioritize recommended fixes by risk and blast radius. Each fix should include severity, rationale, cited files, effort estimate, and implementation guidance.
|
|
5. If evidence is incomplete because large or binary files were skipped, say so explicitly and avoid overclaiming.
|
|
6. Secret-like snippets must remain redacted. Do not reconstruct or expose credentials.
|
|
|
|
Return concise JSON-compatible prose fields only. Do not include markdown fences.
|