dropseed/plain-bug
.claude/skills/plain-bug/SKILL.md
Submit a bug report for the Plain framework. Use when the user wants to report a bug, error, or unexpected behavior. Collects context and creates a GitHub issue.
$ install --global
skillsauthnpx skillsauth add dropseed/plain plain-bugInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 5:21 PM16.0s1 file scanned
SKILL.md
- name:
- plain-bug
- description:
- Submit a bug report for the Plain framework. Use when the user wants to report a bug, error, or unexpected behavior. Collects context and creates a GitHub issue.
Submit a Plain Bug Report
1. Get bug details from the user
Ask the user for:
- Title (required) — a short summary of the bug
- Description (required) — what happened and how to trigger it.
Keep it concise but include whichever of these are available:
- Reproduction steps — a minimal code snippet or command sequence that triggers the bug. Most valuable when the bug is reproducible.
- Actual error — the traceback or unexpected output verbatim (trimmed to the relevant parts).
- Root cause / fix — if you have high-confidence insight, include it. Helps maintainers triage faster.
Not every bug will have all three — a feature that's missing or behaves incorrectly may just need a clear description.
2. Collect environment info
Run these commands to auto-detect environment details:
uv run plain --version
uv run python --version
uname -s -r
3. Confirm with user
Show the user the full issue title and body before submitting. Do NOT submit without explicit approval.
4. Submit via gh
Create the issue using the GitHub CLI:
gh issue create --repo dropseed/plain --title "<title>" --body "<body>"
The body should follow this format:
<user's bug description>
## Environment
- Plain: <version>
- Python: <version>
- OS: <uname output>
---
*Submitted via the `/plain-bug` skill.*
5. Report the result
Show the issue URL returned by gh so the user can follow up.
Guidelines
- No private info — Don't include file paths, env vars, API keys, secrets, database URLs, or other project-specific details. Only include Plain/Python versions, OS, and the bug description.
- Confirm before submitting — Always show the full issue body to the user and get approval before creating.
- No label needed — Maintainers will triage and label the issue.
Related Skills
dropseed/plainx-release
documentation
VerifiedTrustedCommunity
Releases plainx packages with version suggestions, changelog generation, and git tagging. Use when releasing a package to PyPI.
848SKILL.mdUpdated Apr 15, 2026
dropseed/release
data-ai
VerifiedTrustedCommunity
Releases Plain packages with intelligent version suggestions and parallel release notes generation. Use when releasing packages to PyPI.
848SKILL.mdUpdated Apr 15, 2026
dropseed/plain-upgrade
data-ai
VerifiedTrustedCommunity
Upgrades Plain packages and applies required migration changes. Use when updating to newer package versions.
848SKILL.mdUpdated Apr 15, 2026
dropseed/plain-postgres-doctor
testing
VerifiedTrustedCommunity
Check overall database health — schema correctness and operational health. Use when asked to check the database, validate schema, optimize indexes, or diagnose Postgres problems.
848SKILL.mdUpdated Apr 15, 2026