TiXL Ticket Processor
tixl3d/tixl
Works through the In progress column of the TiXL road-map board unattended, turning simple tickets into git stashes and writing plans for the rest under .agentic/Plans.
Drive the @swamp/issue-lifecycle model for interactive issue triage and plan iteration against swamp-club lab issues.
Install Issue Lifecycle
The automated check flagged lines worth reading first. See the safety section below.
$ npx skills add swamp-club/swamp --skill issue-lifecycle -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install swamp-club/swamp issue-lifecycle --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/swamp-club/swamp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/issue-lifecycle .claude/skills/issue-lifecycle && 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-lifecycle" agent skill from https://github.com/swamp-club/swamp/tree/main/.claude/skills/issue-lifecycle into .claude/skills/issue-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-lifecycle", 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/swamp-club/swamp/tree/main/.claude/skills/issue-lifecycleType 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 swamp-club/swamp --skill issue-lifecycle -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install swamp-club/swamp issue-lifecycle --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swamp-club/swamp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/issue-lifecycle .agents/skills/issue-lifecycle && 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-lifecycle" agent skill from https://github.com/swamp-club/swamp/tree/main/.claude/skills/issue-lifecycle into .agents/skills/issue-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-lifecycle", 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 swamp-club/swamp --skill issue-lifecycle -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install swamp-club/swamp issue-lifecycle --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swamp-club/swamp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/issue-lifecycle .cursor/skills/issue-lifecycle && 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-lifecycle" agent skill from https://github.com/swamp-club/swamp/tree/main/.claude/skills/issue-lifecycle into .cursor/skills/issue-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-lifecycle", 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/swamp-club/swamp.git --path .claude/skills/issue-lifecycle--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 swamp-club/swamp --skill issue-lifecycle -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install swamp-club/swamp issue-lifecycle --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swamp-club/swamp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/issue-lifecycle .gemini/skills/issue-lifecycle && 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-lifecycle" agent skill from https://github.com/swamp-club/swamp/tree/main/.claude/skills/issue-lifecycle into .gemini/skills/issue-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-lifecycle", 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 swamp-club/swamp issue-lifecycleInstalls 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 swamp-club/swamp --skill issue-lifecycle -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/swamp-club/swamp.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/issue-lifecycle .github/skills/issue-lifecycle && 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-lifecycle" agent skill from https://github.com/swamp-club/swamp/tree/main/.claude/skills/issue-lifecycle into .github/skills/issue-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-lifecycle", 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 swamp-club/swamp --skill issue-lifecycle -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install swamp-club/swamp issue-lifecycle --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swamp-club/swamp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/issue-lifecycle .opencode/skills/issue-lifecycle && 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-lifecycle" agent skill from https://github.com/swamp-club/swamp/tree/main/.claude/skills/issue-lifecycle into .opencode/skills/issue-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-lifecycle", 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-lifecycle- GitHub stars
- 646
- Token cost
- ~4.6k tokens
- SKILL.md length
- 1,927 words
- Files
- 8 (incl. references)
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Drive the @swamp/issue-lifecycle model for interactive issue triage and plan iteration against swamp-club lab issues.
- Works in 6 steps: Triage (steps 1–4) → Planning (steps 5–7) → Adversarial Review & Iteration → …
- The user wants to triage a swamp-club issue
- SKILL.md covers Core Principles, Prepare to Ship (Ad-Hoc Work), Several Issues, One Piece of… and Repository Configuration, plus 6 more sections
- Calls git, deno and gh
What it does
Issue Lifecycle is an agent skill from swamp-club/swamp. Drive the @swamp/issue-lifecycle model for interactive issue triage and plan iteration against swamp-club lab issues. Use when the user wants to triage a swamp-club issue, generate an implementation plan, or iterate on a plan with feedback. Also handles retroactive lifecycle creation for ad-hoc work via "prepare to ship", carrying several issues through one lifecycle when the same work fixes them (linkissue), and shipping a duplicate of an already-shipped issue with its fix instead of closing it (markduplicate)…
Its SKILL.md is about 4.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `references/adversarial-review.md`, `references/code-conformance-review.md` and `references/implementation.md`).
It sits in Agent Workflows, covering Issue triage and Planning. It works with Deno. The repository describes itself as: Stinemates, Watson, Adam, Mahir, Paul.
When your agent uses it
- The user wants to triage a swamp-club issue
- Generate an implementation plan
- Iterate on a plan with feedback
- Issue lifecycle
Example prompts
- “prepare to ship”
- “triage issue”
- “triage”
- “/issue-lifecycle”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
- Triage (steps 1–4)
- Planning (steps 5–7)
- Adversarial Review & Iteration
- Implementation & Code Conformance Review
- Contributor Notification
- Session Summary
What it can do on your machine
Read from SKILL.md and the folder at commit 986f902. 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:
gitdenogh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and 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
Issue Lifecycle loads about 4.6k tokens when it runs, and up to ~15k if it reads all its reference files. Until then it costs about 209 tokens; SKILL.md has 1,927 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: warnings
The automated check found patterns that need a careful read before installing.
- WarningTells the agent its actions are pre-authorized / not to stop for confirmationSKILL.md:75
**This flow is fully automatic — do not ask for confirmation at each step.**
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,927 words (~4,633 tokens).
“Interactive triage and implementation planning for swamp-club lab issues using the @swamp/issue-lifecycle extension model. This skill drives the model conversationally — the human steers, you execute.”
- name
- issue-lifecycle
Files
SKILL.md and 7 other files (references) in .claude/skills/issue-lifecycle of swamp-club/swamp.
- SKILL.md
- references/adversarial-review.md
- references/code-conformance-review.md
- references/implementation.md
- references/linked-issues.md
- references/planning.md
- references/triage.md
- references/verification.md
Open the folder on GitHubat commit 986f902
Compare with similar skills
Issue Lifecycle 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 Lifecycle this skillswamp-club/swamp | 646 | — | ~4.6k | Automated safety check: Warn | Custom licence | |
| TiXL Ticket Processortixl3d/tixl | 5.1k | — | ~2.6k | Automated safety check: Pass | MIT | |
| OpenSpec Guided OnboardingFission-AI/OpenSpec | 72k | 1 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Paseo Committeegetpaseo/paseo | 20k | 1 repos | ~496 | Automated safety check: Pass | Custom licence | |
| Improvefossasia/eventyay-interpretation | 1.6k | 10 repos | ~3.7k | Automated safety check: Warn | MIT | |
| Bd To Br MigrationDicklesworthstone/beads_rust | 1.1k | — | ~2.2k | Automated safety check: Pass | Custom licence |
Similar skills
OpenSpec Guided Onboarding
Fission-AI/OpenSpec
Walks you through a complete OpenSpec workflow cycle with narration while doing real work in your codebase.
Paseo Committee
getpaseo/paseo
Forms a two-agent committee with contrasting profiles to analyze a stuck problem in parallel, reconcile their views and return a consensus plan without editing files.
Improve
fossasia/eventyay-interpretation
Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute.
Bd To Br Migration
Dicklesworthstone/beads_rust
Migrate docs from bd (beads) to br (beadsrust). An agent skill from Dicklesworthstone/beads_rust.
Context Mode Ops
mksglu/context-mode
Runs maintenance for the context-mode project with parallel subagents: issue triage, PR review, releases, bug fixes, announcements and branch syncing.
More from swamp-club/swamp
Ddd
swamp-club/swamp
Domain Driven Design guidance for TypeScript/Deno codebases.
GitHub PR
swamp-club/swamp
Create and manage GitHub pull requests. An agent skill from swamp-club/swamp.
Swamp
swamp-club/swamp
Swamp CLI — create and run models, build and validate workflows, query and manage data, store and retrieve vault secrets, develop and publish extensions, initialize repos, run reports, file issues…
Swamp Getting Started
swamp-club/swamp
Interactive getting-started walkthrough for new swamp users.
Terminal Output
swamp-club/swamp
Terminal output design system for swamp CLI commands. An agent skill from swamp-club/swamp.
Jujutsu
swamp-club/swamp
Track changes, rebase modifications, resolve conflicts, and manage bookmarks with Jujutsu (jj).
Related
Works with
Categories
Questions about Issue Lifecycle
What does Issue Lifecycle do?
Drive the @swamp/issue-lifecycle model for interactive issue triage and plan iteration against swamp-club lab issues. Issue Lifecycle is an agent skill from swamp-club/swamp. Drive the @swamp/issue-lifecycle model for interactive issue triage and plan iteration against swamp-club lab issues.
When should I use Issue Lifecycle?
Issue Lifecycle fits situations like: the user wants to triage a swamp-club issue; generate an implementation plan; iterate on a plan with feedback; issue lifecycle.
How do I install Issue Lifecycle in Claude Code?
Run `npx skills add swamp-club/swamp --skill issue-lifecycle -a claude-code`. Or copy the skill folder (.claude/skills/issue-lifecycle in swamp-club/swamp) into .claude/skills/issue-lifecycle in your project. Claude Code loads it when a task matches its description.
How do I install Issue Lifecycle in Codex?
Run `npx skills add swamp-club/swamp --skill issue-lifecycle -a codex`. Or copy the skill folder (.claude/skills/issue-lifecycle in swamp-club/swamp) into .agents/skills/issue-lifecycle in your project. Codex loads it when a task matches its description.
Can I use Issue Lifecycle 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 swamp-club/swamp --skill issue-lifecycle -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-lifecycle, .gemini/skills/issue-lifecycle, .github/skills/issue-lifecycle and .opencode/skills/issue-lifecycle in your project.
What does Issue Lifecycle need to run?
Going by SKILL.md and its folder, Issue Lifecycle needs the command-line tools its instructions call (git, deno and gh).
Does Issue Lifecycle access the network?
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Issue Lifecycle safe to install?
Our automated static check of SKILL.md flagged 1 warning(s): tells the agent its actions are pre-authorized / not to stop for confirmation. Read the flagged lines before installing; the check is not a guarantee either way.
What licence does Issue Lifecycle use?
Issue Lifecycle has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Issue Lifecycle use?
About 4.6k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 10k tokens, read only when the agent opens those files.
What are the alternatives to Issue Lifecycle?
Skills that share tags, products or a category with Issue Lifecycle: TiXL Ticket Processor (tixl3d/tixl, 5.1k stars), OpenSpec Guided Onboarding (Fission-AI/OpenSpec, 72k stars), Paseo Committee (getpaseo/paseo, 20k stars) and Improve (fossasia/eventyay-interpretation, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Issue Lifecycle?
swamp-club (a GitHub organization) maintains it in swamp-club/swamp, which has 646 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 9, 2026.
Source: swamp-club/swamp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.