New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Coffee GB Compatibility Fix

by trekawek in trekawek/coffee-gb

Takes a Coffee GB compatibility issue from reproduction through a tested fix to an isolated pull request, with issue follow-up and screenshot evidence when possible.

MITAuto-check passedDevelopment

Install Coffee GB Compatibility Fix

skills CLI
$ npx skills add trekawek/coffee-gb --skill fix-compatibility-issue -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install trekawek/coffee-gb fix-compatibility-issue --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/trekawek/coffee-gb.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/fix-compatibility-issue .claude/skills/fix-compatibility-issue && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
fix-compatibility-issue
GitHub stars
1.2k
Token cost
~1.4k tokens
SKILL.md length
796 words
Files
2
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

Takes a Coffee GB compatibility issue from reproduction through a tested fix to an isolated pull request, with issue follow-up and screenshot evidence when possible.

  • Works in 6 steps: Read and classify the issue → Isolate the work → Reproduce before editing → …
  • Fixing a specific Coffee GB game or ROM compatibility issue on GitHub
  • SKILL.md covers 1. Read and classify the issue, 2. Isolate the work, 3. Reproduce before editing and 4. Investigate and fix the cause, plus 2 more sections
  • Calls gh

What it does

The agent handles one GitHub issue per branch and pull request. It requires an issue number or URL, reads the title, body, comments, labels, linked PRs and attachments, and records the ROM title and region, hardware mode, expected and observed behavior, reproduction steps, save data and timing needs. Copyrighted ROM data is never published, and a missing ROM is looked up in `./roms/gb` or `./roms/gbc` by title, platform, region, revision and checksum without silently substituting a similar one. If information is insufficient and no ROM matches, it comments with what is missing and stops.

Work happens on a clean branch cut from the remote default branch and named with a `codex/issue-` prefix, number and short slug. The agent reproduces before editing, using the controller Agent API from `CLAUDE.md`, records the configuration, commit, ROM checksum, inputs and frame bounds, adds the narrowest deterministic regression test it can and captures a baseline screenshot at a stable frame for visual bugs. Hardware-backed test suites outrank other emulators, which are only diagnostic evidence. Screenshot uploads go through the repository's `gitshot` skill, and the excerpt ends before the fix and submission steps.

When your agent uses it

  • Fixing a specific Coffee GB game or ROM compatibility issue on GitHub
  • Reproducing an emulator bug deterministically before changing timing code
  • Preparing a pull request with a regression test and visual evidence

Example prompts

  • “Fix the compatibility issue reported in Coffee GB issue number 215.”
  • “Reproduce the graphical glitch from this issue and add a regression test.”
  • “Read the new Game Boy Color compatibility issue and tell me whether we have the ROM to test it.”

Requirements

  • A checkout of the Coffee GB repository
  • The gh CLI with GitHub access
  • A ROM matching the issue under ./roms

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Read and classify the issue
  2. Isolate the work
  3. Reproduce before editing
  4. Investigate and fix the cause
  5. Create the pull request
  6. Update the original issue

What it can do on your machine

Read from SKILL.md and the folder at commit 554ea56. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Coffee GB Compatibility Fix loads about 1.4k tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 796 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~70
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from trekawek/coffee-gb at commit 554ea56, republished under its MIT licence (© trekawek). 796 words, ~1,411 tokens.

Download SKILL.mdSave it as .claude/skills/fix-compatibility-issue/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
fix-compatibility-issue
description
Reproduce, investigate, fix, test, and submit a Coffee GB game or ROM compatibility issue as an isolated GitHub pull request, with issue follow-up and visual evidence when possible. Use when asked to address a specific Coffee GB GitHub compatibility issue.

Fix Compatibility Issue

Handle one GitHub issue per branch and pull request. Preserve evidence from the failing behavior through the verified fix.

Use the repository gitshot skill at ../gitshot/SKILL.md for every GitHub screenshot upload. Read it before publishing visual evidence, inspect each image first, and follow its public-upload privacy warning.

1. Read and classify the issue

  1. Require an issue number or URL, then read its title, body, comments, labels, linked PRs, and every supplied attachment with gh issue view and the GitHub API as needed.
  2. Record the affected ROM title and region/revision, DMG/CGB/SGB mode, expected behavior, observed behavior, reproduction steps, save state or save data, and any timing or input requirements.
  3. Check whether the issue includes a legally usable ROM or a precise ROM identity. Never publish or attach copyrighted ROM data.
  4. If no ROM is included, locate it in ./roms/gb or ./roms/gbc. Match title, platform, region, revision, and checksum when the issue provides them. Do not substitute a similarly named ROM silently.
  5. Read the relevant technical sections of CLAUDE.md and doc/derived/ before changing timing-sensitive CPU, PPU/STAT, APU, timer, or interrupt behavior.

If the issue lacks enough information and no matching ROM exists in the local database, comment with the missing details and stop instead of guessing.

2. Isolate the work

  1. Ensure the working tree is clean and fetch the remote default branch.
  2. Create a branch from the current remote default branch named codex/issue-<number>-<short-slug>.
  3. Keep unrelated user changes and unrelated issue fixes out of the branch.

3. Reproduce before editing

Follow the issue steps on the reported hardware mode and ROM revision. Prefer the controller Agent API and the integration support mains described in CLAUDE.md for deterministic runs.

  • Capture exact emulator configuration, commit, ROM checksum, inputs, frame/tick bounds, and observed output.
  • Add the narrowest useful automated regression test when the behavior can be asserted deterministically.
  • For a visual defect, capture a baseline screenshot at a stable frame. Do not use a different ROM revision or a nondeterministic frame as evidence.
  • Compare traces, memory, frames, or audio with hardware-backed test suites and independent references as appropriate. Another emulator is diagnostic evidence, not the compatibility specification.

If automation cannot reproduce the issue after reasonable attempts, do not change code or create a speculative PR. Add an issue comment beginning with **AI-generated comment:** that summarizes the ROM identity/checksum, environment, steps attempted, observed result, and states: The problem could not be reproduced by automation and will be triaged manually. Leave the issue open and stop.

Show full SKILL.md (377 more words)Show less

4. Investigate and fix the cause

Trace the smallest subsystem that explains the divergence and establish why the current behavior is wrong before editing it. Prefer a general hardware-compatible correction over a game-specific workaround.

  • Keep the patch scoped to the issue.
  • Preserve save-state mementos when adding state.
  • Add or update a regression test that fails before and passes after the fix whenever practical.
  • Remove temporary probes, debug output, generated files, ROMs, save data, and scratch artifacts before committing.

Run the focused regression test, affected module tests, and relevant integration profiles. For timing, interrupt, PPU, APU, or mapper changes, run the broader compatibility suites identified in CLAUDE.md in proportion to the risk. Record exact commands and results.

Re-run the original reproduction steps. For a visible fix, capture one stable after-fix screenshot showing the corrected state; prefer the same frame/configuration as the baseline.

5. Create the pull request

Review the diff and commit only the scoped source and test changes. Push the issue branch and create a non-draft PR against the default branch.

The PR description must explain:

  • the compatibility symptom and affected ROM/mode;
  • the root cause and why the old behavior was incorrect;
  • what the patch changes and why it is the appropriate fix;
  • regression coverage and all test commands/results;
  • Fixes #<issue> when the PR genuinely resolves the issue;
  • the after-fix screenshot when one exists and can be uploaded.

For a visible compatibility fix, upload the stable evidence with gitshot and embed the returned Markdown in the PR description. Prefer a labelled before/after comparison when both frames are deterministic and safe to publish. If the upload fails, record the failure rather than committing screenshots to manufacture a URL.

Do not claim hardware accuracy beyond the evidence collected.

6. Update the original issue

After the PR URL exists, add a short issue comment beginning with **AI-generated comment:**. Link the PR and summarize the fix in one or two sentences. Use gitshot to attach or embed the after-fix screenshot. If it cannot be uploaded, do not commit the image merely to manufacture a URL; mention the upload failure in the PR and keep the issue note concise.

Finally report the branch, commit, PR URL, tests, reproduction result, and screenshot status. Do not merge the PR as part of this skill.

© trekawek, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .agents/skills/fix-compatibility-issue of trekawek/coffee-gb.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 554ea56

Compare with similar skills

Coffee GB Compatibility Fix next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Coffee GB Compatibility Fix compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Coffee GB Compatibility Fix this skilltrekawek/coffee-gb1.2k—~1.4kAutomated safety check: PassMIT
Exposed Bug Fix WorkflowJetBrains/Exposed9.3k—~3.8kAutomated safety check: PassApache-2.0
Issue TracerZaxbyHub/opencode-swarm493—~4.4kAutomated safety check: PassMIT
Pre-Release PR Triagejamiepine/voicebox57k—~3.1kAutomated safety check: PassMIT
React Router Bug Fix Workflowremix-run/react-router57k—~1.3kAutomated safety check: PassMIT
Ouroboros Maintainer TriageQ00/ouroboros6.2k—~1.7kAutomated safety check: PassMIT

Similar skills

  • Exposed Bug Fix Workflow

    JetBrains/Exposed

    Official

    Takes a GitHub or YouTrack issue for the Exposed project through reproduction, a failing test, a fix, validation and a pull request.

    9.3k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Issue Tracer

    ZaxbyHub/opencode-swarm

    Drives a bug report from validation and root-cause tracing through a critic-reviewed plan, an approved minimal fix and a PR-ready closure, never merging without recorded human approval.

    493 GitHub stars~4.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Pre-Release PR Triage

    jamiepine/voicebox

    Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.

    57k GitHub stars~3.1k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • React Router Bug Fix Workflow

    remix-run/react-router

    Fixes a React Router bug reported in a GitHub issue end to end: fetching the issue, validating the reproduction, writing a failing test and implementing the fix on a new branch.

    57k GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed

  • Ouroboros Maintainer Triage

    Q00/ouroboros

    Triages and works through GitHub issues and pull requests in the Q00/ouroboros repo as a maintainer, within a stated review boundary and clear limits on what it may change.

    6.2k GitHub stars~1.7k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • PR Triage

    rtk-ai/rtk

    Audits a repository's open pull requests, deep-reviews chosen ones and drafts review comments that are only posted after you approve them.

    83k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check: notes

More from trekawek/coffee-gb

  • Game Boy ROM Playthrough Driver

    trekawek/coffee-gb

    Plays an authorized Game Boy or Game Boy Color ROM in one persistent headless Coffee GB session, inspecting frames and keeping an action trace for replay or tests.

    1.2k GitHub stars~1.3k tokensUpdated 7 days ago
    Auto-check passed

  • Coffee GB Release

    trekawek/coffee-gb

    Releases the current Coffee GB Maven snapshot through the GitHub Maven release workflow, then verifies and curates the tag and GitHub release.

    1.2k GitHub stars~1.4k tokensUpdated 7 days ago
    Auto-check passed

  • Gitshot Image Uploader

    trekawek/coffee-gb

    Uploads screenshots and other images from the terminal and returns markdown-ready URLs to embed in GitHub pull requests, issues and comments.

    1.2k GitHub stars~855 tokensUpdated 7 days ago
    Auto-check passed

  • Merge Pull Request

    trekawek/coffee-gb

    Validates a GitHub pull request, rebases away conflicts, waits for required CI on the final commit, merges with rebase and cleans up the topic branch.

    1.2k GitHub stars~903 tokensUpdated 7 days ago
    Auto-check passed

Works with

Categories

Questions about Coffee GB Compatibility Fix

What does Coffee GB Compatibility Fix do?

Takes a Coffee GB compatibility issue from reproduction through a tested fix to an isolated pull request, with issue follow-up and screenshot evidence when possible. The agent handles one GitHub issue per branch and pull request. It requires an issue number or URL, reads the title, body, comments, labels, linked PRs and attachments, and records the ROM title and region, hardware mode, expected and observed behavior, reproduction steps, save data and timing needs.

When should I use Coffee GB Compatibility Fix?

Coffee GB Compatibility Fix fits situations like: fixing a specific Coffee GB game or ROM compatibility issue on GitHub; reproducing an emulator bug deterministically before changing timing code; preparing a pull request with a regression test and visual evidence.

How do I install Coffee GB Compatibility Fix in Claude Code?

Run `npx skills add trekawek/coffee-gb --skill fix-compatibility-issue -a claude-code`. Or copy the skill folder (.agents/skills/fix-compatibility-issue in trekawek/coffee-gb) into .claude/skills/fix-compatibility-issue in your project. Claude Code loads it when a task matches its description.

How do I install Coffee GB Compatibility Fix in Codex?

Run `npx skills add trekawek/coffee-gb --skill fix-compatibility-issue -a codex`. Or copy the skill folder (.agents/skills/fix-compatibility-issue in trekawek/coffee-gb) into .agents/skills/fix-compatibility-issue in your project. Codex loads it when a task matches its description.

Can I use Coffee GB Compatibility Fix in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add trekawek/coffee-gb --skill fix-compatibility-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fix-compatibility-issue, .gemini/skills/fix-compatibility-issue, .github/skills/fix-compatibility-issue and .opencode/skills/fix-compatibility-issue in your project.

What does Coffee GB Compatibility Fix need to run?

Going by SKILL.md and its folder, Coffee GB Compatibility Fix needs the command-line tools its instructions call (gh). Our summary lists: A checkout of the Coffee GB repository; The gh CLI with GitHub access; A ROM matching the issue under ./roms.

Does Coffee GB Compatibility Fix access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Coffee GB Compatibility Fix safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Coffee GB Compatibility Fix use?

Coffee GB Compatibility Fix is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Coffee GB Compatibility Fix use?

About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Coffee GB Compatibility Fix?

Skills that share tags, products or a category with Coffee GB Compatibility Fix: Exposed Bug Fix Workflow (JetBrains/Exposed, 9.3k stars), Issue Tracer (ZaxbyHub/opencode-swarm, 493 stars), Pre-Release PR Triage (jamiepine/voicebox, 57k stars) and React Router Bug Fix Workflow (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Coffee GB Compatibility Fix?

trekawek (a GitHub user) maintains it in trekawek/coffee-gb, which has 1,170 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 1, 2026.

Source: trekawek/coffee-gb on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.