error-tracker-install

Install and configure gh-issue-tracker to report errors as GitHub Issues.

2|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/zot24/skills --skill error-tracker-install
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: error-tracker-install
Source: https://github.com/zot24/skills/tree/main/skills/gh-issue-tracker/skills/gh-issue-tracker
Command: npx skills add https://github.com/zot24/skills --skill error-tracker-install

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

gh-issue-tracker enables error reporting by turning runtime errors into GitHub Issues, simplifying visibility, triage, and collaboration across teams.

Core Features & Use Cases

  • Guides architecture decisions (server-only vs client+server) to determine where errors are captured and reported.
  • Provides framework-specific setup steps for Next.js, Express, and vanilla Node.js workflows.
  • Manages environment variables and repository permissions securely, with clear guidance on token usage and proxy patterns for client-side reporting.
  • Step-by-step installation, configuration, and verification to ensure proper error reporting and easy maintenance.

Quick Start

Install gh-issue-tracker in your project, set GITHUB_TOKEN and GITHUB_REPO, then follow the framework-specific setup steps to enable server-side error reporting.

Frequently Asked Questions about error-tracker-install

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

FAQPage Schema
How do I report Node.js runtime errors as GitHub Issues?▼

To track runtime errors as GitHub Issues, install gh-issue-tracker, set the GITHUB_TOKEN and GITHUB_REPO environment variables, and follow the framework-specific setup steps to enable server-side error reporting and triage.

How do I set up error tracking in a Next.js or Express application?▼

Error tracking in Next.js or Express requires installing gh-issue-tracker and following framework-specific integration steps to capture server-side runtime errors and report them directly to your GitHub repository.

What GitHub token permissions do I need to create issues for error tracking?▼

To automate error reporting as GitHub Issues, you need a GitHub token with Issues permissions and a target repository configured via environment variables to securely authenticate and post runtime errors.

Can I report client-side errors to GitHub Issues without exposing my token?▼

Client-side error reporting to GitHub Issues requires a server-side proxy pattern, keeping your GitHub token secure on the server while routing client error reports through your Node.js backend to avoid exposure.

Should I capture errors on the server only or on both client and server?▼

Choosing between server-only and client+server error capture depends on your architecture; server-only handles backend errors securely, while client+server uses proxy patterns to safely capture and route frontend runtime errors as GitHub Issues.

What environment variables are required to configure GitHub issue tracking?▼

Configuring GitHub issue tracking requires setting the GITHUB_TOKEN and GITHUB_REPO environment variables to authenticate the error tracker and post runtime errors to the correct target repository.