leeovery/workflow-log-bug
skills/workflow-log-bug/SKILL.md
Capture a bug report as a markdown file in the workflow inbox. Use when the user wants to log, note, or save a bug for later.
$ install --global
skillsauthnpx skillsauth add leeovery/claude-technical-workflows workflow-log-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 28, 2026, 1:22 PM136.0s1 file scanned
SKILL.md
- name:
- workflow-log-bug
- description:
- Capture a bug report as a markdown file in the workflow inbox. Use when the user wants to log, note, or save a bug for later.
- allowed-tools:
- Bash(mkdir -p)
This skill captures a bug report and writes it to the inbox.
If there's already conversation context about something broken, synthesise it straight into the file without asking questions. If this is a cold start, ask what's broken and have a natural back-and-forth to draw out the symptoms. Recognise when it has enough detail (typically 2-4 exchanges) and wrap up.
Capture only — these are rules, not guidelines:
- Do not read code or explore the codebase
- Do not search the web or fetch external resources
- Do not attempt to reproduce or validate the bug
- Do not suggest fixes or workarounds
- Do not diagnose root causes or theorise about what's wrong
- Do not propose solutions or next steps
When ready, generate a short kebab-case slug from the core symptom (e.g., stale-cache-on-deploy, login-timeout) and write the file:
mkdir -p .workflows/.inbox/bugs
File: .workflows/.inbox/bugs/{YYYY-MM-DD}--{slug}.md (use today's actual date)
- H1 title, prose body, 200-500 words
- No forced headings — let the content flow naturally
- Naturally cover symptoms, conditions, and impact as discussed
- Mention relevant codebase files if they came up
Confirm with a one-liner:
Output the next fenced block as a code block:
Logged bug: {slug}
Related Skills
leeovery/workflow-discovery
tools
VerifiedTrustedCommunity
--- name: workflow-discovery user-invocable: false allowed-tools: Bash(node .claude/skills/workflow-discovery/scripts/discovery.cjs), Bash(node .claude/skills/workflow-manifest/scripts/manifest.cjs), Bash(node .claude/skills/workflow-knowledge/scripts/knowledge.cjs), Bash(git status), Bash(git add), Bash(git commit), Bash(cp), Bash(mkdir -p .workflows/), Bash(mv .workflows/.inbox/) --- # Discovery The universal first phase. Shape the work the user is bringing — confirm what kind of work it is,
21SKILL.mdUpdated Jun 3, 2026
leeovery/workflow-continue-quickfix
tools
VerifiedTrustedCommunity
--- name: workflow-continue-quickfix user-invocable: false allowed-tools: Bash(node .claude/skills/workflow-continue-quickfix/scripts/discovery.cjs), Bash(node .claude/skills/workflow-manifest/scripts/manifest.cjs), Bash(node .claude/skills/workflow-knowledge/scripts/knowledge.cjs) --- Continue an in-progress quick-fix. Determines current phase and routes to the appropriate phase skill. > **⚠️ ZERO OUTPUT RULE**: Do not narrate your processing. Produce no output until a step or reference file
21SKILL.mdUpdated Jun 3, 2026
leeovery/workflow-continue-feature
tools
VerifiedTrustedCommunity
--- name: workflow-continue-feature user-invocable: false allowed-tools: Bash(node .claude/skills/workflow-continue-feature/scripts/discovery.cjs), Bash(node .claude/skills/workflow-manifest/scripts/manifest.cjs), Bash(node .claude/skills/workflow-knowledge/scripts/knowledge.cjs) --- Continue an in-progress feature. Determines current phase and routes to the appropriate phase skill. > **⚠️ ZERO OUTPUT RULE**: Do not narrate your processing. Produce no output until a step or reference file expl
21SKILL.mdUpdated Jun 3, 2026
leeovery/workflow-continue-epic
tools
VerifiedTrustedCommunity
--- name: workflow-continue-epic user-invocable: false allowed-tools: Bash(node .claude/skills/workflow-continue-epic/scripts/discovery.cjs), Bash(node .claude/skills/workflow-manifest/scripts/manifest.cjs), Bash(node .claude/skills/workflow-knowledge/scripts/knowledge.cjs), Bash(node .claude/skills/workflow-legacy-research-split/scripts/detect.cjs), Bash(node .claude/skills/workflow-discovery/scripts/discovery.cjs) --- Continue an in-progress epic. Shows full phase-by-phase state and routes to
21SKILL.mdUpdated Jun 3, 2026