Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

fix-github-issue

Estrellas988

Forks202

Actualizado22 de enero de 2026 a las 21:04

Fix GitHub issues using gh CLI. Use when asked to fix, resolve, or address a GitHub issue. Creates fixes on separate branches, runs tests locally, and creates PRs when tests pass. Requires gh CLI authenticated and repo cloned locally.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

freekmurze

freekmurze/dotfiles

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	fix-github-issue
description	Fix GitHub issues using gh CLI. Use when asked to fix, resolve, or address a GitHub issue. Creates fixes on separate branches, runs tests locally, and creates PRs when tests pass. Requires gh CLI authenticated and repo cloned locally.

GitHub Issue Fixer

Fix GitHub issues by implementing solutions on feature branches with proper testing.

Prerequisites

gh CLI installed and authenticated
Repository cloned locally
Test command available (auto-detected or specified)

Workflow

1. Understand the Issue

gh issue view <issue-number>

Read the issue thoroughly.

2. Create Feature Branch

git checkout main && git pull origin main
git checkout -b fix-<short-description>

Branch naming: fix-description (lowercase, hyphens).

3. Analyze the Codebase

Before coding, understand the relevant parts:

Locate files related to the issue
Check existing tests for patterns
Review any referenced code in the issue

4. Implement the Fix

Make minimal, focused changes that address the issue. Follow existing code style and patterns.

5. Run Tests Locally

Detect and run the test suite. Most likely it will be pest or phpunit. Take a look what is defined in composer.json or the testing github file.

Tests must pass locally before proceeding. If tests fail:

Analyze failures
Fix the implementation
Re-run until all pass

6. Commit Changes

git add -A
git commit -m "Fix #<issue-number>: <concise description>"

Use conventional commit message referencing the issue number.

7. Push and Create PR

git push -u origin fix/issue-<issue-number>-<short-description>
gh pr create --title "Fix #<issue-number>: <title>" --body "Fixes #<issue-number>

## Changes
- <bullet points of changes>

## Testing
- All local tests pass
- <any additional testing done>"

8. Monitor CI

gh pr checks --watch

If CI fails:

Review the failure: gh run view <run-id> --log-failed
Fix locally
Push additional commits
Repeat until CI passes

Quick Reference

# View issue
gh issue view 123

# Create branch
git checkout -b fix/issue-123-description

# After fixing and tests pass
git add -A && git commit -m "Fix #123: description"
git push -u origin fix/issue-123-description
gh pr create --fill

# Watch CI
gh pr checks --watch

Más de este repositorio

mismo repositorio

php-guidelines-from-spatie

freekmurze/dotfiles

Describes PHP and Laravel guidelines provided by Spatie. These rules result in more maintainable, and readable code.

2026-07-15988

mailcoach

freekmurze/dotfiles

Manage email marketing with the Mailcoach CLI — email lists, subscribers, campaigns, transactional emails, templates, automations, tags, and segments.

2026-06-04988

typefully

freekmurze/dotfiles

Create, schedule, and manage social media posts via Typefully. ALWAYS use this skill when asked to draft, schedule, post, or check tweets, posts, threads, or social media content for Twitter/X, LinkedIn, Threads, Bluesky, or Mastodon.

2026-05-04988

update-spatie-docs

freekmurze/dotfiles

Update Spatie package documentation on spatie.be by re-importing docs for a given repo. Use after merging a PR that touches docs/, or when the user says 'update docs for [package]', 'rebuild docs for [repo]', 'import docs for [repo]', or invokes /update-spatie-docs [repo-name]. Takes a repo name argument (e.g., 'backup', 'laravel-medialibrary', 'laravel-pdf').

2026-05-04988

ad-creative

freekmurze/dotfiles

When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' or 'ad performance optimization.' This skill covers generating ad creative at scale, iterating based on performance data, and enforcing platform character limits. For campaign strategy and targeting, see paid-ads. For landing page copy, see copywriting.

2026-04-23988

ai-seo

freekmurze/dotfiles

When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' or 'zero-click search.' This skill covers content optimization for AI answer engines, monitoring AI visibility, and getting cited as a source. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema-markup.

2026-04-23988

name	fix-github-issue
description	Fix GitHub issues using gh CLI. Use when asked to fix, resolve, or address a GitHub issue. Creates fixes on separate branches, runs tests locally, and creates PRs when tests pass. Requires gh CLI authenticated and repo cloned locally.

GitHub Issue Fixer

Fix GitHub issues by implementing solutions on feature branches with proper testing.

Prerequisites

gh CLI installed and authenticated
Repository cloned locally
Test command available (auto-detected or specified)

Workflow

1. Understand the Issue

gh issue view <issue-number>

Read the issue thoroughly.

2. Create Feature Branch

git checkout main && git pull origin main
git checkout -b fix-<short-description>

Branch naming: fix-description (lowercase, hyphens).

3. Analyze the Codebase

Before coding, understand the relevant parts:

Locate files related to the issue
Check existing tests for patterns
Review any referenced code in the issue

4. Implement the Fix

Make minimal, focused changes that address the issue. Follow existing code style and patterns.

5. Run Tests Locally

Detect and run the test suite. Most likely it will be pest or phpunit. Take a look what is defined in composer.json or the testing github file.

Tests must pass locally before proceeding. If tests fail:

Analyze failures
Fix the implementation
Re-run until all pass

6. Commit Changes

git add -A
git commit -m "Fix #<issue-number>: <concise description>"

Use conventional commit message referencing the issue number.

7. Push and Create PR

git push -u origin fix/issue-<issue-number>-<short-description>
gh pr create --title "Fix #<issue-number>: <title>" --body "Fixes #<issue-number>

## Changes
- <bullet points of changes>

## Testing
- All local tests pass
- <any additional testing done>"

8. Monitor CI

gh pr checks --watch

If CI fails:

Review the failure: gh run view <run-id> --log-failed
Fix locally
Push additional commits
Repeat until CI passes

Quick Reference

# View issue
gh issue view 123

# Create branch
git checkout -b fix/issue-123-description

# After fixing and tests pass
git add -A && git commit -m "Fix #123: description"
git push -u origin fix/issue-123-description
gh pr create --fill

# Watch CI
gh pr checks --watch