Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

fix-github-issue

Estrelas0

Forks0

Atualizado10 de janeiro de 2026 às 07:59

Investigate and fix a GitHub issue using gh, then validate with tests and create a PR. Use when a user references a GitHub issue number or asks to fix an issue.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

whywaita

whywaita/dotfiles

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	fix-github-issue
description	Investigate and fix a GitHub issue using gh, then validate with tests and create a PR. Use when a user references a GitHub issue number or asks to fix an issue.

Fix GitHub Issue

Workflow

Read the issue with gh issue view (include comments and labels as needed).
Restate the problem and expected behavior succinctly.
Search the codebase for relevant files and logic.
Implement the fix with minimal scope changes.
Add or update tests to cover success and failure paths.
Run tests, lint, and type checks appropriate to the repo.
Create a commit and PR following the commit-push-pr workflow.

Notes

Use gh for all GitHub interactions (issues, PRs, checks).
If the issue lacks repro steps, add a small reproduction section in the PR notes.

Mais deste repositório

mesmo repositório

poker-hand-review

whywaita/dotfiles

ポーカーのハンドレビューと座学を統合的に行うスキル。ユーザのハンドをGTO Wizardのソルバーデータとブログ記事を根拠に多角的にレビューし、同時に集合分析ベースの体系的な座学を実施する。数学的根拠（ポットオッズ、エクイティ、EV計算）とexploit観点を含む。「ハンドレビューして」「このハンドどう思う？」「レビューお願い」「hand review」「この判断正しかった？」「座学したい」「このスポットを勉強したい」「集合分析を見たい」「深掘りして勉強」「このスポットの全体像を知りたい」

2026-04-190

commit-push-pr

whywaita/dotfiles

Create a git commit, push a branch, and open a Pull Request with gh. Use when asked to commit changes, push to origin, or create PRs, especially when conventional commits and PR templates are required.

2026-04-060

design-to-spec

whywaita/dotfiles

設計ドキュメント（Design Doc）を実装可能な仕様書（Spec）に変換するスキル。「なぜ作るか」を「何を作るか」に変換し、実装者・QA・保守者が参照できる明確な仕様を生成する。「スペックにまとめて」「仕様書にして」「実装仕様を書いて」「specに変換して」でトリガーすること。 dig で曖昧さを解消してから使用すると最も効果的。

2026-04-060

dig

whywaita/dotfiles

既存の設計ドキュメント・RFC・計画書を読み込み、AskUserQuestion による構造化された質問を通じて、曖昧さ・矛盾・未定義事項を洗い出し、決定事項と残課題を整理するスキル。「深掘りして」「曖昧な点を洗い出して」「設計の穴を突いて」「challenge my assumptions」「ドキュメントを読んで質問して」のような依頼でトリガーすること。仕様書（spec）の生成が目的の場合は design-to-spec を使うこと。

name	fix-github-issue
description	Investigate and fix a GitHub issue using gh, then validate with tests and create a PR. Use when a user references a GitHub issue number or asks to fix an issue.

Fix GitHub Issue

Workflow

Read the issue with gh issue view (include comments and labels as needed).
Restate the problem and expected behavior succinctly.
Search the codebase for relevant files and logic.
Implement the fix with minimal scope changes.
Add or update tests to cover success and failure paths.
Run tests, lint, and type checks appropriate to the repo.
Create a commit and PR following the commit-push-pr workflow.

Notes

Use gh for all GitHub interactions (issues, PRs, checks).
If the issue lacks repro steps, add a small reproduction section in the PR notes.