bugreport

Download and analyze ConnectStats bug reports by parsing logs and querying SQLite databases.

84|16|Updated Jan 6, 2018
One-click install
npx skills add https://github.com/roznet/connectstats --skill bugreport
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bugreport
Source: https://github.com/roznet/connectstats/tree/main/.claude/skills/bugreport
Command: npx skills add https://github.com/roznet/connectstats --skill bugreport

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of downloading, analyzing, and summarizing bug reports from the ConnectStats application, enabling faster identification and resolution of user-reported issues.

Core Features & Use Cases

  • Automated Bug Report Download: Fetches bug report data directly from the ConnectStats server.
  • Log and Database Analysis: Parses log files and queries local SQLite databases to pinpoint errors and anomalies.
  • Use Case: When a user reports a problem with their fitness data in ConnectStats, this Skill can be invoked with a bug report ID to quickly gather all relevant diagnostic information, present it clearly, and suggest initial hypotheses for the root cause.

Quick Start

Use the bugreport skill to analyze bug report ID 142.

Frequently Asked Questions about bugreport

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

FAQPage Schema
How do I debug a ConnectStats mobile app issue using a bug report ID?

Debug a ConnectStats mobile app issue by providing the bug report ID to automatically download, extract metadata, parse logs, and query SQLite databases to pinpoint anomalies. This process quickly surfaces diagnostic information for user-reported problems.

Why does ConnectStats experience a silent activity drop or missing summary values?

Silent activity drops or missing summary values in ConnectStats are typically caused by data anomalies or parsing errors. Analyzing the bug report logs and querying the local SQLite database identifies whether NaN values or sync failures are the root cause.

What's the best way to analyze FIT file re-download loops in a mobile app log?

Analyze FIT file re-download loops by parsing the mobile app log files within the downloaded bug report. The Skill identifies repetitive sync patterns and database errors to suggest initial hypotheses for the looping behavior.

Do I need specific command-line tools to parse SQLite databases and log files from bug reports?

Yes, parsing bug reports requires specific command-line tools like jq and unzip, along with environment variables for authentication. These dependencies are necessary to extract metadata and query the associated SQLite databases locally.

Can I diagnose database errors from a user's bug report without manually opening SQLite files?

Yes, you can diagnose database errors without manual SQLite inspection by running the automated bug report analysis. The Skill queries the local SQLite databases directly to extract and summarize relevant error logs and anomalies.

What is a bug report analysis workflow for diagnosing mobile app fitness data issues?

A bug report analysis workflow for mobile app fitness data issues involves downloading the report with an ID, extracting metadata, parsing logs, and querying SQLite databases to present clear diagnostic information and root cause hypotheses.