Foreman Debug
VisionForge-OU/foreman
Headless root-cause debugging loop for a Foreman worker whose tests, build, or acceptance check are failing — especially on a retry.
A skill your agent uses when bugfix-request.json exists - validate, reproduce, root-cause, and enqueue a user-reported bug as a category=bugfix feature, then chain to Worker for TDD fix
Install Long Task Hotfix
$ npx skills add suriyel/longtaskforagent --skill long-task-hotfix -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install suriyel/longtaskforagent long-task-hotfix --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/suriyel/longtaskforagent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/long-task-hotfix .claude/skills/long-task-hotfix && 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 "long-task-hotfix" agent skill from https://github.com/suriyel/longtaskforagent/tree/main/skills/long-task-hotfix into .claude/skills/long-task-hotfix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "long-task-hotfix", 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/suriyel/longtaskforagent/tree/main/skills/long-task-hotfixType 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 suriyel/longtaskforagent --skill long-task-hotfix -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install suriyel/longtaskforagent long-task-hotfix --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/suriyel/longtaskforagent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/long-task-hotfix .agents/skills/long-task-hotfix && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "long-task-hotfix" agent skill from https://github.com/suriyel/longtaskforagent/tree/main/skills/long-task-hotfix into .agents/skills/long-task-hotfix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "long-task-hotfix", 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 suriyel/longtaskforagent --skill long-task-hotfix -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install suriyel/longtaskforagent long-task-hotfix --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/suriyel/longtaskforagent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/long-task-hotfix .cursor/skills/long-task-hotfix && 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 "long-task-hotfix" agent skill from https://github.com/suriyel/longtaskforagent/tree/main/skills/long-task-hotfix into .cursor/skills/long-task-hotfix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "long-task-hotfix", 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/suriyel/longtaskforagent.git --path skills/long-task-hotfix--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 suriyel/longtaskforagent --skill long-task-hotfix -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install suriyel/longtaskforagent long-task-hotfix --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/suriyel/longtaskforagent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/long-task-hotfix .gemini/skills/long-task-hotfix && 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 "long-task-hotfix" agent skill from https://github.com/suriyel/longtaskforagent/tree/main/skills/long-task-hotfix into .gemini/skills/long-task-hotfix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "long-task-hotfix", 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 suriyel/longtaskforagent long-task-hotfixInstalls 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 suriyel/longtaskforagent --skill long-task-hotfix -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/suriyel/longtaskforagent.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/long-task-hotfix .github/skills/long-task-hotfix && 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 "long-task-hotfix" agent skill from https://github.com/suriyel/longtaskforagent/tree/main/skills/long-task-hotfix into .github/skills/long-task-hotfix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "long-task-hotfix", 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 suriyel/longtaskforagent --skill long-task-hotfix -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install suriyel/longtaskforagent long-task-hotfix --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/suriyel/longtaskforagent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/long-task-hotfix .opencode/skills/long-task-hotfix && 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 "long-task-hotfix" agent skill from https://github.com/suriyel/longtaskforagent/tree/main/skills/long-task-hotfix into .opencode/skills/long-task-hotfix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "long-task-hotfix", 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
long-task-hotfix- GitHub stars
- 177
- Token cost
- ~2.2k tokens
- SKILL.md length
- 966 words
- Files
- 1
- Skills in repo
- 17
- Repo updated
- First seen
- Licence
- None found
At a glance
A skill your agent uses when bugfix-request.json exists - validate, reproduce, root-cause, and enqueue a user-reported bug as a category=bugfix feature, then chain to Worker for TDD fix
- Works in 8 steps: Announce → Validate Signal File → Orient → …
- Bugfix-request.json exists - validate
- SKILL.md covers Step 1: Announce, Step 2: Validate Signal File, Step 3: Orient and Step 4: Reproduce, plus 7 more sections
- Calls python and git
What it does
Long Task Hotfix is an agent skill from suriyel/longtaskforagent. Use when bugfix-request.json exists - validate, reproduce, root-cause, and enqueue a user-reported bug as a category=bugfix feature, then chain to Worker for TDD fix
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Root cause analysis and Test-driven development.
When your agent uses it
- Bugfix-request.json exists - validate
- Enqueue a user-reported bug as a category=bugfix feature
- Then chain to Worker for TDD fix
Example prompts
- “/long-task-hotfix”
Requirements
- Python 3
Workflow steps
8 steps, taken from the step headings in SKILL.md.
- Announce
- Validate Signal File
- Orient
- Reproduce
- Root Cause Analysis
- Enqueue as Bugfix Feature
- Update task-progress.md
- Finalize
What it can do on your machine
Read from SKILL.md and the folder at commit ca67fe1. 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:
pythongit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, 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
Long Task Hotfix loads about 2.2k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 966 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); files beside SKILL.md are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 966 words (~2,226 tokens).
“You are using the long-task-hotfix skill. This skill handles bugs found during user manual testing.”
- name
- long-task-hotfix
Files
Just SKILL.md in skills/long-task-hotfix of suriyel/longtaskforagent.
Open the folder on GitHubat commit ca67fe1
Compare with similar skills
Long Task Hotfix 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 |
|---|---|---|---|---|---|---|
| Long Task Hotfix this skillsuriyel/longtaskforagent | 177 | — | ~2.2k | Automated safety check: Pass | None | |
| Foreman DebugVisionForge-OU/foreman | 443 | — | ~1.1k | Automated safety check: Pass | Custom licence | |
| Opsmill Dev Test Driving Bugsopsmill/infrahub | 531 | — | ~4k | Automated safety check: Pass | Apache-2.0 | |
| Systematic Debuggingforyourhealth111-pixel/Vibe-Skills | 3.6k | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Ij Debuggerxpinjection/test-driven-spring-boot | 112 | — | ~6.4k | Automated safety check: Pass | MIT | |
| Context Modes0xNyk/lacp | 305 | — | ~313 | Automated safety check: Pass | MIT |
Similar skills
Opsmill Dev Test Driving Bugs
opsmill/infrahub
Writes a single failing test that reproduces a bug after its root-cause analysis is complete, before any fix is written.
Systematic Debugging
foryourhealth111-pixel/Vibe-Skills
Root-cause route for actual bugs, failing tests, build errors, crashes, stack traces, and unexpected behavior.
Ij Debugger
xpinjection/test-driven-spring-boot
Debugger-first runtime root-cause analysis for JVM code in IntelliJ IDEA.
Context Modes
0xNyk/lacp
Structured work modes for agent sessions. An agent skill from 0xNyk/lacp.
Omk Coding
KaimingWan/oh-my-kiro
Enforces coding best practices: deep-read before modify, LSP-first navigation, TDD red-green-refactor, minimal changes, self-review, verification.
More from suriyel/longtaskforagent
All 17 skills in this repoLong Task Init
suriyel/longtaskforagent
A skill your agent uses when ATS doc exists (or auto-skipped) but feature-list.json not yet created - scaffold project artifacts and populate features from Design §10.2
Long Task Explore
suriyel/longtaskforagent
A skill your agent uses for on-demand deep exploration of an existing codebase - analyzes architecture, data flow, domain model, API surface, dependencies, and code health
Long Task TDD
suriyel/longtaskforagent
A skill your agent uses when implementing a feature through TDD in a long-task project - enforces Red-Green-Refactor cycle
Using Long Task
suriyel/longtaskforagent
A skill your agent uses when starting any session in a long-task project - routes to the correct phase skill based on project state
Long Task Ats
suriyel/longtaskforagent
A skill your agent uses when design doc exists but no ATS doc and no feature-list.json - generate a global Acceptance Test Strategy mapping every requirement to acceptance scenarios with category…
Long Task Design
suriyel/longtaskforagent
A skill your agent uses when SRS doc exists but no design doc and no feature-list.json - take the approved SRS as input and produce an architecture/design document focused on HOW to build it
Related
Categories
Questions about Long Task Hotfix
What does Long Task Hotfix do?
A skill your agent uses when bugfix-request.json exists - validate, reproduce, root-cause, and enqueue a user-reported bug as a category=bugfix feature, then chain to Worker for TDD fix. Long Task Hotfix is an agent skill from suriyel/longtaskforagent.
When should I use Long Task Hotfix?
Long Task Hotfix fits situations like: bugfix-request.json exists - validate; enqueue a user-reported bug as a category=bugfix feature; then chain to Worker for TDD fix.
How do I install Long Task Hotfix in Claude Code?
Run `npx skills add suriyel/longtaskforagent --skill long-task-hotfix -a claude-code`. Or copy the skill folder (skills/long-task-hotfix in suriyel/longtaskforagent) into .claude/skills/long-task-hotfix in your project. Claude Code loads it when a task matches its description.
How do I install Long Task Hotfix in Codex?
Run `npx skills add suriyel/longtaskforagent --skill long-task-hotfix -a codex`. Or copy the skill folder (skills/long-task-hotfix in suriyel/longtaskforagent) into .agents/skills/long-task-hotfix in your project. Codex loads it when a task matches its description.
Can I use Long Task Hotfix 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 suriyel/longtaskforagent --skill long-task-hotfix -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/long-task-hotfix, .gemini/skills/long-task-hotfix, .github/skills/long-task-hotfix and .opencode/skills/long-task-hotfix in your project.
What does Long Task Hotfix need to run?
Going by SKILL.md and its folder, Long Task Hotfix needs the command-line tools its instructions call (python and git). Our summary lists: Python 3.
Does Long Task Hotfix access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Long Task Hotfix 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 Long Task Hotfix use?
No licence was found for Long Task Hotfix or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Long Task Hotfix use?
About 2.2k tokens (SKILL.md is roughly 8.9k 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 Long Task Hotfix?
Skills that share tags, products or a category with Long Task Hotfix: Foreman Debug (VisionForge-OU/foreman, 443 stars), Opsmill Dev Test Driving Bugs (opsmill/infrahub, 531 stars), Systematic Debugging (foryourhealth111-pixel/Vibe-Skills, 3.6k stars) and Ij Debugger (xpinjection/test-driven-spring-boot, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Long Task Hotfix?
suriyel (a GitHub user) maintains it in suriyel/longtaskforagent, which has 177 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on June 23, 2026.
Source: suriyel/longtaskforagent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.