gspdev-prompt-audit

Analyze prompt files for semantic quality issues and generate an audit report.

49|4|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/jubscodes/get-shit-pretty --skill gspdev-prompt-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gspdev-prompt-audit
Source: https://github.com/jubscodes/get-shit-pretty/tree/main/dev/skills/gspdev-prompt-audit
Command: npx skills add https://github.com/jubscodes/get-shit-pretty --skill gspdev-prompt-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Semantic quality issues in GSP prompt files are detected and surfaced to prevent vague, conflicting, or redundant instructions from degrading AI outputs.

Core Features & Use Cases

  • Detect dead weight and remove instructions that the model already follows by default.
  • Flag contradictions and inconsistencies across skills and agents to ensure coherent behavior.
  • Perform cross-file analysis to surface global patterns and duplication, enabling consolidation.
  • Generate a structured audit report written to dev/reports/prompt-audit.md, guiding remediation.

Quick Start

Run a baseline audit on prompts and generate the report at dev/reports/prompt-audit.md.

Frequently Asked Questions about gspdev-prompt-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit prompt files for semantic quality issues?

Auditing prompt files for semantic quality involves analyzing them to detect dead weight, contradictions, one-off patches, vagueness, and repetition, then generating a structured report to guide remediation.

What is cross-file prompt analysis and when do I need it?

Cross-file prompt analysis surfaces global patterns, inconsistencies, and duplication across skills and agents to enable consolidation. You need it when coherent AI behavior across multiple prompts is required.

How do I generate a prompt audit report for my agents?

Generate a prompt audit report by running an analysis scoped to agents or specific named files, which enforces baseline checks and per-file semantic criteria, writing the detailed output to dev/reports/prompt-audit.md.

Can I limit the semantic prompt audit to specific named files?

Yes, you can limit the audit scope to skills, agents, or specific named prompt files to target the analysis and produce a focused semantic quality report for those exact files.

Why does my AI output degrade despite having detailed prompt instructions?

AI output degradation often stems from semantic quality issues in prompt files such as vague instructions, contradictions, or redundant dead weight that conflict with the model's default behavior.

What's the best way to detect contradictions across multiple prompt files?

The best way to detect contradictions across multiple prompt files is performing a cross-file analysis that flags inconsistencies across skills and agents to ensure coherent behavior and surface duplication.