Debugging CI Failures
PostHog/posthog
Debugs failing GitHub Actions CI runs for PostHog PRs, commits, and branches, and answers broad CI-health questions ("is CI red?", "is master green today?", "what's broken right now?").
A skill your agent uses when the user asks to fix a bug, references a GitHub issue number, or describes an issue and wants a fix.
Install Issue To Regression Test
$ npx skills add brunosabot/streamline-card --skill issue-to-regression-test -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brunosabot/streamline-card issue-to-regression-test --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brunosabot/streamline-card.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/issue-to-regression-test .claude/skills/issue-to-regression-test && rm -rf skills-srcUse ~/.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/
Install the "issue-to-regression-test" agent skill from https://github.com/brunosabot/streamline-card/tree/main/.agents/skills/issue-to-regression-test into .claude/skills/issue-to-regression-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-to-regression-test", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brunosabot/streamline-card/tree/main/.agents/skills/issue-to-regression-testType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brunosabot/streamline-card --skill issue-to-regression-test -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brunosabot/streamline-card issue-to-regression-test --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brunosabot/streamline-card.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/issue-to-regression-test .agents/skills/issue-to-regression-test && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "issue-to-regression-test" agent skill from https://github.com/brunosabot/streamline-card/tree/main/.agents/skills/issue-to-regression-test into .agents/skills/issue-to-regression-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-to-regression-test", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brunosabot/streamline-card --skill issue-to-regression-test -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brunosabot/streamline-card issue-to-regression-test --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brunosabot/streamline-card.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/issue-to-regression-test .cursor/skills/issue-to-regression-test && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "issue-to-regression-test" agent skill from https://github.com/brunosabot/streamline-card/tree/main/.agents/skills/issue-to-regression-test into .cursor/skills/issue-to-regression-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-to-regression-test", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brunosabot/streamline-card.git --path .agents/skills/issue-to-regression-test--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brunosabot/streamline-card --skill issue-to-regression-test -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brunosabot/streamline-card issue-to-regression-test --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brunosabot/streamline-card.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/issue-to-regression-test .gemini/skills/issue-to-regression-test && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "issue-to-regression-test" agent skill from https://github.com/brunosabot/streamline-card/tree/main/.agents/skills/issue-to-regression-test into .gemini/skills/issue-to-regression-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-to-regression-test", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brunosabot/streamline-card issue-to-regression-testInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brunosabot/streamline-card --skill issue-to-regression-test -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brunosabot/streamline-card.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/issue-to-regression-test .github/skills/issue-to-regression-test && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "issue-to-regression-test" agent skill from https://github.com/brunosabot/streamline-card/tree/main/.agents/skills/issue-to-regression-test into .github/skills/issue-to-regression-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-to-regression-test", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brunosabot/streamline-card --skill issue-to-regression-test -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brunosabot/streamline-card issue-to-regression-test --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brunosabot/streamline-card.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/issue-to-regression-test .opencode/skills/issue-to-regression-test && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "issue-to-regression-test" agent skill from https://github.com/brunosabot/streamline-card/tree/main/.agents/skills/issue-to-regression-test into .opencode/skills/issue-to-regression-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-to-regression-test", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
issue-to-regression-test- GitHub stars
- 269
- Token cost
- ~529 tokens
- SKILL.md length
- 185 words
- Files
- 3 (incl. scripts)
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when the user asks to fix a bug, references a GitHub issue number, or describes an issue and wants a fix.
- Works in 4 steps: Scaffold the Regression Test → Refine and Reproduce the Bug → Fix the Bug → …
- The user asks to fix a bug
- SKILL.md covers Workflow and Example JSDoc
- Runs JavaScript scripts from its folder; calls node and npx
What it does
Issue To Regression Test is an agent skill from brunosabot/streamline-card. Use this skill when the user asks to fix a bug, references a GitHub issue number, or describes an issue and wants a fix. This skill will guide you through fetching the issue details, scaffolding a standard regression test, writing a failing test, fixing the issue, and verifying that all tests pass. Make sure to use this skill whenever a bug fix is requested.
Its SKILL.md is about 530 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `evals/evals.json` and `scripts/scaffold-test.js`).
It sits in Testing & QA, covering Project scaffolding, Debugging and Failing and flaky tests. It works with GitHub, Home Assistant and Vitest. The repository describes itself as: Streamline your Lovelace configuration with with a card template system. The licence is MIT.
When your agent uses it
- The user asks to fix a bug
- References a GitHub issue number
- Describes an issue and wants a fix
- A bug fix is requested
Example prompts
- “/issue-to-regression-test”
Requirements
- Node.js
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Scaffold the Regression Test
- Refine and Reproduce the Bug
- Fix the Bug
- Verify Fix and Prevent Regressions
What it can do on your machine
Read from SKILL.md and the folder at commit 3a2667f. 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
Ships 1 file in scripts/ (JavaScript), which the agent can run.
Shell commands in SKILL.md call:
nodenpx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx, 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
Issue To Regression Test loads about 529 tokens when it runs. Until then it costs about 96 tokens; SKILL.md has 185 words of instructions outside code blocks.
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); the scripts in this folder are not scanned.
SKILL.md
The full file from brunosabot/streamline-card at commit 3a2667f, republished under its MIT licence (© brunosabot). 185 words, ~529 tokens.
Download SKILL.mdSave it as
.claude/skills/issue-to-regression-test/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- issue-to-regression-test
- description
- Use this skill when the user asks to fix a bug, references a GitHub issue number, or describes an issue and wants a fix. This skill will guide you through fetching the issue details, scaffolding a standard regression test, writing a failing test, fixing the issue, and verifying that all tests pass. Make sure to use this skill whenever a bug fix is requested.
Issue to Regression Test
This skill automates the workflow of fixing a bug reported via a GitHub issue by creating a regression test first.
Workflow
Scaffold the Regression Test:
- If an issue number is provided, use the bundled Node.js script to scaffold the test file.
- Command:
node .agents/skills/issue-to-regression-test/scripts/scaffold-test.js <issue_number> - This script will automatically fetch issue details using
ghand create a file insrc/tests/with the correct JSDoc header.
Refine and Reproduce the Bug:
- Open the newly created test file in
src/tests/. - Implement a test case that fails when run against the current codebase.
- The test should accurately reflect the bug described in the issue.
- Use
vitestfor testing. Importdescribe,expect,itfromvitest. - Import necessary modules from
src/to test the failing behavior.
- Open the newly created test file in
Fix the Bug:
- Modify the source code in the
src/directory to fix the reported bug. - Aim for a surgical fix that solves the problem without unnecessary refactoring.
- Modify the source code in the
Verify Fix and Prevent Regressions:
- Ensure the new test passes.
- Run ALL tests in the project to ensure no regressions were introduced.
- Command:
npx vitest run
Example JSDoc
/**
* Regression test for issue #2: Visibility settings from template are not respected
* https://github.com/brunosabot/streamline-card/issues/2
*
* Bug: When configuring visibility in a template, the card would always be visible
* instead of respecting the visibility conditions.
*
* Expected: Visibility settings from templates should be properly applied to the card
*/© brunosabot, 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 2 other files (scripts) in .agents/skills/issue-to-regression-test of brunosabot/streamline-card.
- SKILL.md
- evals/evals.json
- scripts/scaffold-test.js
Open the folder on GitHubat commit 3a2667f
Compare with similar skills
Issue To Regression Test 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Issue To Regression Test this skillbrunosabot/streamline-card | 269 | — | ~529 | Automated safety check: Pass | MIT | |
| Debugging CI FailuresPostHog/posthog | 40k | — | ~5.8k | Automated safety check: Pass | Custom licence | |
| Bug To Patch GeneratorArabelaTso/Skills-4-SE | 253 | — | ~4.4k | Automated safety check: Pass | Apache-2.0 | |
| React Router Bug Fix Workflowremix-run/react-router | 57k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Exposed Bug Fix WorkflowJetBrains/Exposed | 9.3k | — | ~3.8k | Automated safety check: Pass | Apache-2.0 | |
| CI/CD Failure Troubleshootingruby-git/ruby-git | 1.8k | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
- Official
Bug To Patch Generator
ArabelaTso/Skills-4-SE
Generate code fixes and patches from bug reports, failing test cases, error messages, and stack traces.
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.
- Official
Exposed Bug Fix Workflow
JetBrains/Exposed
Takes a GitHub or YouTrack issue for the Exposed project through reproduction, a failing test, a fix, validation and a pull request.
CI/CD Failure Troubleshooting
ruby-git/ruby-git
Diagnoses and fixes failing GitHub Actions runs by identifying the failure, fetching only the relevant logs, finding the root cause and reproducing it locally.
Development
web-infra-dev/rstest
Feature and bug-fix development checklist for the Rstest monorepo.
More from brunosabot/streamline-card
Changelog Generator
brunosabot/streamline-card
Generate an engaging, human-centric, and community-focused changelog from git history.
Related
Works with
Categories
Questions about Issue To Regression Test
What does Issue To Regression Test do?
A skill your agent uses when the user asks to fix a bug, references a GitHub issue number, or describes an issue and wants a fix. Issue To Regression Test is an agent skill from brunosabot/streamline-card. Use this skill when the user asks to fix a bug, references a GitHub issue number, or describes an issue and wants a fix.
When should I use Issue To Regression Test?
Issue To Regression Test fits situations like: the user asks to fix a bug; references a GitHub issue number; describes an issue and wants a fix; A bug fix is requested.
How do I install Issue To Regression Test in Claude Code?
Run `npx skills add brunosabot/streamline-card --skill issue-to-regression-test -a claude-code`. Or copy the skill folder (.agents/skills/issue-to-regression-test in brunosabot/streamline-card) into .claude/skills/issue-to-regression-test in your project. Claude Code loads it when a task matches its description.
How do I install Issue To Regression Test in Codex?
Run `npx skills add brunosabot/streamline-card --skill issue-to-regression-test -a codex`. Or copy the skill folder (.agents/skills/issue-to-regression-test in brunosabot/streamline-card) into .agents/skills/issue-to-regression-test in your project. Codex loads it when a task matches its description.
Can I use Issue To Regression Test 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 brunosabot/streamline-card --skill issue-to-regression-test -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/issue-to-regression-test, .gemini/skills/issue-to-regression-test, .github/skills/issue-to-regression-test and .opencode/skills/issue-to-regression-test in your project.
What does Issue To Regression Test need to run?
Going by SKILL.md and its folder, Issue To Regression Test needs JavaScript for the scripts in its folder and the command-line tools its instructions call (node and npx). Our summary lists: Node.js.
Does Issue To Regression Test access the network?
SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Issue To Regression Test 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Issue To Regression Test use?
Issue To Regression Test 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 Issue To Regression Test use?
About 529 tokens (SKILL.md is roughly 2.1k 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 Issue To Regression Test?
Skills that share tags, products or a category with Issue To Regression Test: Debugging CI Failures (PostHog/posthog, 40k stars), Bug To Patch Generator (ArabelaTso/Skills-4-SE, 253 stars), React Router Bug Fix Workflow (remix-run/react-router, 57k stars) and Exposed Bug Fix Workflow (JetBrains/Exposed, 9.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Issue To Regression Test?
brunosabot (a GitHub user) maintains it in brunosabot/streamline-card, which has 269 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on May 24, 2026.
Source: brunosabot/streamline-card on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.