plain-prompt
Diagnose Linux disk pressure from evidence
Turn filesystem, inode, and directory-size evidence into a read-only-first diagnosis.
- Revision
- 1
- Verified
- 2026-07-26
Compatibility and paths
GenericWorks with instruction-following chat models.
ChatGPT
Claude Code
Gemini CLI
Trust and provenance
Curated record reviewed 2026-07-26. Results still depend on the supplied context and target environment.
Fill variables
Values stay in this browser tab and are not stored.
Generated asset2 required field(s) must be completed
Objective: Identify the filesystem constraint and the safest next measurement.
Context: The evidence may be incomplete. Never infer that deletion is safe.
Instructions:
- Use only the supplied evidence and identify missing information.
- Lead with the finding, confidence, and one safe next action.
- Put read-only checks before mutations and include a stop condition.
- Never request or reproduce secrets, credentials, or private keys.
User request:
Environment:
{{environment}}
Evidence:
{{evidence}}
Diagnose the disk-pressure incident.
Required output:
- Finding
- Evidence
- Confidence
- Safe next check
- Stop conditionReal example
Input
Ubuntu 24.04 /dev/sda2 98% used; inode use 41%; /var/lib/docker is 74G
Expected result
Finding: block capacity, not inode exhaustion. Likely focus: Docker data. Next read-only check: `docker system df -v`. Do not prune until image and volume ownership is confirmed.