skills.rest
auroralabs-loci
auroralabs-lociOFFICIAL
Explore all skills by this author →
WebsiteGitHub

bug-report

Collect forensic diagnostic data for LOCI failures into a timestamped markdown report.

1|Updated May 19, 2026
Search Tags:#debugging#plugin#environment#diagnostics#bug-report#loci#forensic-report
One-click install
npx skills add https://github.com/auroralabs-loci/loci-claude --skill bug-report-auroralabs-loci
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-report
Source: https://github.com/auroralabs-loci/loci-claude/tree/main/skills/bug-report
Command: npx skills add https://github.com/auroralabs-loci/loci-claude --skill bug-report-auroralabs-loci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When LOCI analyses fail, skills do not trigger, or results are missing or invalid, it is hard to gather the right environment and project state to diagnose the root cause; this Skill automates a thorough forensic snapshot and writes a sanitized, timestamped diagnostic report that can be shared for debugging.

Core Features & Use Cases

  • Environment snapshot: Captures claude version, model ID, plugin version, OS info, project context, LOCI paths, setup markers, git state, and hooks configuration.
  • 12-point diagnostics checklist: Runs checks for MCP visibility, session context, compiler and architecture detection, venv and asm-analyze health, build artifacts, hooks validity, and quota usage with clear PASS/FAIL details.
  • Safe local forensics: Uses only local Read and shell operations (Read, Bash, Glob, Grep), avoids MCP tool use, sanitizes secrets and home paths, and writes a redacted markdown report for sharing or reloading into Claude Code.
  • Use cases: Run after a failed analysis, when a skill did not auto-invoke, when MCP is unreachable, or whenever a developer needs a complete, reproducible failure snapshot.

Quick Start

Ask the plugin "bug report" followed by a one-sentence description of what failed.

Frequently Asked Questions about bug-report

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

FAQPage Schema
How do I generate a forensic diagnostic report for a failed LOCI plugin analysis?▼

To generate a forensic diagnostic report for a failed LOCI plugin analysis, trigger the bug-report command with a one-sentence failure description. The skill runs a 12-point diagnostics checklist, captures an environment snapshot, and writes a timestamped markdown report.

Why does my LOCI skill not trigger or return missing analysis results?▼

When LOCI skills do not trigger or return missing results, a forensic diagnostic report helps identify the root cause. The skill checks MCP visibility, session context, venv health, and hooks validity to pinpoint why the analysis failed.

Does the LOCI diagnostics report require remote MCP calls or external dependencies?▼

The LOCI diagnostics report does not require remote MCP calls or external dependencies. It performs only safe local read and shell operations using Read, Bash, Glob, and Grep to gather environment snapshots and run diagnostics.

What is the best way to capture environment and session state for debugging LOCI failures?▼

The best way to capture session state for debugging LOCI failures is running a local forensic snapshot. It collects claude version, OS info, plugin version, git state, and venv python paths into a sanitized, reproducible markdown file.

Can I share a diagnostic bug report without exposing local secrets and home directory paths?▼

You can share the diagnostic bug report safely because the forensic snapshot sanitizes secrets and redacts home directory paths. The resulting timestamped markdown file is stripped of sensitive information for secure sharing.

What checks are included in the 12-point diagnostics checklist for LOCI plugin sessions?▼

The 12-point diagnostics checklist for LOCI plugin sessions includes checks for MCP visibility, session context, compiler and architecture detection, venv and asm-analyze health, build artifacts, hooks validity, and quota usage with clear PASS or FAIL details.

Related Skills

Explore More Software Engineering Skills→
bitwize-music-studiobitwize-music-studio
408

setup

Detect Python environments and configure venv dependencies for the Claude Music plugin.

Official
Intermediate
PiaoxuemoliPiaoxuemoli

systematic-debugging

Guide root cause analysis through a four-phase debugging process.

Community
Advanced
cuiosscuioss
1

cui-diagnostic-patterns

Enforce Glob, Read, and Grep instead of Bash for file operations.

Community
Advanced
NagyViktNagyVikt
2

using-git-worktrees

Create and manage isolated git worktrees for parallel branch development.

Community
Advanced