القائمة
Summarizes an stlinspector InspectionReport (JSON) for a non-technical stakeholder. Use when asked to "summarize", "explain", or "triage" an inspection report.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Domain knowledge for mesh validation thresholds and definitions. Use when adding or reviewing checks in core.py.
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Triage GitHub issues through a label-based state machine with interactive grilling sessions. Use when user wants to triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
Auto-triggered security checklist. Activates when editing API endpoint files, configuration files, Dockerfiles, or dependency manifests. Runs a structured security review automatically — no slash command needed.
Break a plan, spec, or PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
Turn the current conversation context into a PRD and submit it as a GitHub issue. Use when user wants to create a PRD from the current context.
| name | inspection-report-summary |
| description | Summarizes an stlinspector InspectionReport (JSON) for a non-technical stakeholder. Use when asked to "summarize", "explain", or "triage" an inspection report. |
Read the JSON report written by --report (e.g. out.json, or the path given): bounding_box, volume, surface_area, triangle_count, and a list of issues (if any).
