skills.rest
mphacker
mphackerCOMMUNITY
Explore all skills by this author →
GitHub

resolve-issue

Resolves GitHub issues in the TeslaUSB project via root-cause analysis and implementation.

54|14|Updated Oct 27, 2025
Search Tags:#automation#github#code-review#root-cause#issue-triage#teslausb
One-click install
npx skills add https://github.com/mphacker/TeslaUSB --skill resolve-issue-mphacker
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resolve-issue
Source: https://github.com/mphacker/TeslaUSB/tree/main/.github/skills/resolve-issue
Command: npx skills add https://github.com/mphacker/TeslaUSB --skill resolve-issue-mphacker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides teams to systematically investigate GitHub issues, perform root-cause analysis, implement fixes or features, and verify outcomes within the TeslaUSB project.

Core Features & Use Cases

  • Structured phase-based analysis from scope resolution through implementation and post-resolution review.
  • Enforces project conventions, branch management, and manual verification when automated tests are unavailable.
  • Useful for single issues, sub-item tasks, and multi-issue triage across open issues.

Quick Start

Describe a GitHub issue to trigger the full root-cause analysis and implementation workflow.

Frequently Asked Questions about resolve-issue

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

FAQPage Schema
How do I automate GitHub issue resolution with root-cause analysis?▼

Fixing TeslaUSB GitHub issues requires diagnosing root causes, implementing fixes, and verifying outcomes. This workflow enforces project conventions, creates a feature branch off main, and performs manual verification when automated tests are unavailable.

Can I triage and fix multiple open GitHub issues in bulk?▼

Resolving multiple open GitHub issues in bulk is supported for the TeslaUSB project. This workflow handles single issues, multi-item sub-tasks, and bulk issue sets across open issues with various labels.

What is the best way to ensure my GitHub code review fixes project conventions?▼

Diagnosing TeslaUSB GitHub issues requires structured phase-based analysis from scope resolution through implementation. This workflow enforces project conventions, creates a feature branch off main, and performs manual verification steps when automation lacks tests.

How do I verify a GitHub issue fix when automation lacks tests?▼

Verifying TeslaUSB GitHub issue fixes without automated tests requires performing manual verification steps. The workflow enforces project conventions by creating a feature branch off main and validating outcomes through a structured post-resolution review.

Does automated issue triage work with the TeslaUSB project?▼

Automated issue triage works with the TeslaUSB project by systematically investigating GitHub issues, performing root-cause analysis, and implementing fixes. It applies structured analysis to single issues and multi-item sub-tasks.

Related Skills

Explore More Software Engineering Skills→
math-incmath-inc
1.2k

github-auth

Configure GitHub authentication via HTTPS tokens, SSH keys, or gh CLI.

Official
Intermediate
blakesimsblakesims

review-merge

Validate feature branch merge readiness with integration checks and summaries.

Community
Advanced
heyallencaoheyallencao
118

ks-verify

Run automated test suites and coverage checks to validate code claims.

Community
Intermediate
spiriMirrorspiriMirror
307

fix-issue

Fix GitHub issues through branching, testing, and pull request workflow.

Official
Intermediate