New: 97,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

Tackle Issue

by yamcodes in yamcodes/arkenv

Automates the process of working on GitHub issues, including branch creation, issue linking, label management, validation, changesets, and PR creation.

MITAuto-check passedDevelopment

Install Tackle Issue

skills CLI
$ npx skills add yamcodes/arkenv --skill tackle-issue -a claude-code

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

GitHub CLI
$ gh skill install yamcodes/arkenv tackle-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/yamcodes/arkenv.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/tackle-issue .claude/skills/tackle-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
tackle-issue
GitHub stars
145
Token cost
~1.1k tokens
SKILL.md length
492 words
Files
1
Skills in repo
20
Repo updated
First seen
Licence
MIT

At a glance

Automates the process of working on GitHub issues, including branch creation, issue linking, label management, validation, changesets, and PR creation.

  • Works in 6 steps: Readiness check & context gathering → Development setup → Implementation → …
  • Development work in your project
  • SKILL.md covers Trigger, Workflow and Best practices
  • Calls gh, pnpm and git

What it does

Tackle Issue is an agent skill from yamcodes/arkenv. Automates the process of working on GitHub issues, including branch creation, issue linking, label management, validation, changesets, and PR creation. Triggered by the command "/tackle-issue ISSUENUMBER".

Its SKILL.md is about 1.1k 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 Development. It works with GitHub. The repository describes itself as: ⛯ Typesafe environment variables with ArkType, Zod, or Valibot. The licence is MIT.

When your agent uses it

  • Development work in your project

Example prompts

  • “/tackle-issue ISSUENUMBER”
  • “Use the tackle-issue skill to automate the process of working on GitHub issues, including branch creation, issue linking, label management…”
  • “/tackle-issue”

Workflow steps

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

  1. Readiness check & context gathering
  2. Development setup
  3. Implementation
  4. Validation & quality assurance
  5. Changeset creation
  6. Pull request creation

What it can do on your machine

Read from SKILL.md and the folder at commit 7340aa2. 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
    • pnpm
    • git

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

  • Network

    No URLs in SKILL.md. Its commands use gh, pnpm and 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

Tackle Issue loads about 1.1k tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 492 words of instructions outside code blocks.

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

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 yamcodes/arkenv at commit 7340aa2, republished under its MIT licence (© yamcodes). 492 words, ~1,054 tokens.

Download SKILL.mdSave it as .claude/skills/tackle-issue/SKILL.md (or your agent's skills folder).
name
tackle-issue
description
Automates the process of working on GitHub issues, including branch creation, issue linking, label management, validation, changesets, and PR creation. Triggered by the command "/tackle-issue ISSUE_NUMBER".
metadata.internal
true

Tackle issue

This skill provides a standardized, rigorous workflow for handling GitHub issues. It ensures that issues are properly vetted before work begins and that all changes meet the project's quality standards before a Pull Request is opened.

Trigger

Use this skill whenever the user says /tackle-issue <number> or asks to "tackle", "handle", or "fix" a specific issue number in a structured way.

Workflow

1. Readiness check & context gathering

Before starting any work, you MUST verify that the issue is ready for an agent.

  1. Retrieve Issue Details: Fetch the issue context, including labels and comments.
    bash
    gh issue view <issue-number> --json title,body,labels,comments
  2. Verify "ready for agent" Label: Check if the ready for agent label is present in the labels array.
    • If the label is MISSING: Abort the process immediately. Inform the user: Issue #<number> is not marked as 'ready for agent'. Please ensure it is fully specified and labeled correctly before proceeding.
    • If the label is PRESENT: Continue to the next step.
2. Development setup
  1. Setup Development Branch: Create and checkout a linked development branch.
    bash
    gh issue develop <issue-number> --checkout
    Note: If a branch already exists, this command will switch to it.
3. Implementation

Proceed with the standard Research -> Strategy -> Execution lifecycle.

  • Research: Understand the issue and surrounding code.
  • Strategy: Plan the fix or feature.
  • Execution: Apply changes surgically. Ensure that:
    • New tests are added to verify the fix or feature.
    • Relevant documentation is updated.
    • JSDoc comments are added or updated for all new or modified functions according to the jsdoc skill.
4. Validation & quality assurance

Once implementation is complete, you MUST run the following validation suite in the project root:

  1. Type Check:
    bash
    pnpm run typecheck
  2. Test Suite:
    bash
    pnpm run test
  3. Lint & Format Check:
    bash
    pnpm run fix

If this step fails (some lint/formatting issues cannot be auto-fixed), you MUST diagnose and fix the errors before proceeding.

Show full SKILL.md (228 more words)Show less
5. Changeset creation

After validation passes, you MUST create a changeset using the changeset skill ONLY if your changes affect a published package, a private package, or anything that gets imported by other packages. Do not create a changeset if the changes are isolated strictly to playgrounds or examples.

  • Determine the appropriate bump type (patch or minor for v0) based on the changeset guidelines.
  • Provide a clear, concise description starting with a #### header.
6. Pull request creation

When the task is complete and validated:

  1. Commit and Push: Stage all changes (including the changeset if created) and push.
    bash
    git add .
git commit -m "fix: tackle issue #<issue-number>"
git push -u origin HEAD
  2. Create Pull Request:
    • Title: Use fix: <issue-title> or feat: <issue-title>.
    • Body: MUST include Fixes #<issue-number> to link the PR to the issue.
    • Labels: Apply relevant labels from the original issue (excluding ready for agent).
    bash
    gh pr create --title "fix: <issue-title>" --body "Fixes #<issue-number>\n\n<brief-description-of-changes>" --label "<labels>"

Best practices

  • Strict Readiness: Never bypass the ready for agent check. It ensures the task is well-defined.
  • Validation First: Never open a PR that fails typecheck, test, or check.
  • Link Everything: Always use gh issue develop and Fixes #<num> for traceability.
  • Changesets: Include a changeset for changes affecting published packages, private packages, or anything imported by other packages. Avoid changesets when changes are isolated to playgrounds or examples.

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

Files

Just SKILL.md in skills/tackle-issue of yamcodes/arkenv.

Open the folder on GitHubat commit 7340aa2

Compare with similar skills

Tackle Issue 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.

Tackle Issue compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tackle Issue this skillyamcodes/arkenv145—~1.1kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Merge Dependabot PRsonyx-dot-app/onyx32k1 repos~2.2kAutomated safety check: PassMIT
Android UI Visual Reviewpermissionlesstech/bitchat-android7.7k—~2.6kAutomated safety check: PassGPL-3.0
Issue Fixmono/SkiaSharp5.6k—~5.1kAutomated safety check: PassMIT
Bug Report TriageOrchestratorInc/agent-orchestrator13k—~1.8kAutomated safety check: PassApache-2.0

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Merge Dependabot PRs

    onyx-dot-app/onyx

    Triages and lands a batch of open Dependabot PRs in the Onyx repo, where main is gated exclusively by GitHub's merge queue: approves and enqueues green PRs, closes superseded duplicates, fixes…

    32k GitHub starsUsed in 1 repo~2.2k tokens
    DevelopmentAuto-check passed

  • Android UI Visual Review

    permissionlesstech/bitchat-android

    Analyze an Android pull request, branch, commit, or patch for user-visible changes and produce reproducible before/after screenshots from isolated builds.

    7.7k GitHub stars~2.6k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Issue Fix

    mono/SkiaSharp

    Fix bugs in SkiaSharp C bindings. An agent skill from mono/SkiaSharp.

    5.6k GitHub stars~5.1k tokensUpdated today
    DevelopmentAuto-check passed

  • Bug Report Triage

    OrchestratorInc/agent-orchestrator

    Helps a reporter describe a bug, searches for duplicates and gathers diagnostic evidence kept separate from a short, human-worded issue draft.

    13k GitHub stars~1.8k tokensUpdated today
    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 yesterday
    DevelopmentAuto-check passed

More from yamcodes/arkenv

All 20 skills in this repo

  • Hallmark

    yamcodes/arkenv

    Anti-AI-slop design skill for greenfield pages, audits, redesigns, and design extraction from URLs or screenshots.

    145 GitHub starsUsed in 4 repos~18k tokens
    Auto-check passed

  • Bulletproof React

    yamcodes/arkenv

    Bulletproof React architecture patterns for scalable, maintainable applications.

    145 GitHub stars~1.8k tokensUpdated 2 days ago
    Auto-check passed

  • Arkenv

    yamcodes/arkenv

    Answer questions about ArkEnv and help implement environment variable validation.

    145 GitHub stars~2.5k tokensUpdated 2 days ago
    Auto-check passed

  • Code Review

    yamcodes/arkenv

    Fetch, analyze, and address code reviews and comments on GitHub, or perform a code review on changes in the workspace.

    145 GitHub stars~1.4k tokensUpdated 2 days ago
    Auto-check passed

  • Forward Port

    yamcodes/arkenv

    Manually forward-ports merged dev (v0) changes to the v1 branch, adapting code to v1's package layout and changeset names.

    145 GitHub stars~970 tokensUpdated 2 days ago
    Auto-check passed

  • Groom Issue

    yamcodes/arkenv

    Groom a poorly written issue by grilling the user to clarify requirements, updating the issue on GitHub via the gh cli, and utilizing the triage skill to apply the correct label and add an agent…

    145 GitHub stars~1k tokensUpdated 2 days ago
    Auto-check passed

Works with

Categories

Questions about Tackle Issue

What does Tackle Issue do?

Automates the process of working on GitHub issues, including branch creation, issue linking, label management, validation, changesets, and PR creation. Tackle Issue is an agent skill from yamcodes/arkenv. Automates the process of working on GitHub issues, including branch creation, issue linking, label management, validation, changesets, and PR creation.

When should I use Tackle Issue?

Tackle Issue fits situations like: development work in your project.

How do I install Tackle Issue in Claude Code?

Run `npx skills add yamcodes/arkenv --skill tackle-issue -a claude-code`. Or copy the skill folder (skills/tackle-issue in yamcodes/arkenv) into .claude/skills/tackle-issue in your project. Claude Code loads it when a task matches its description.

How do I install Tackle Issue in Codex?

Run `npx skills add yamcodes/arkenv --skill tackle-issue -a codex`. Or copy the skill folder (skills/tackle-issue in yamcodes/arkenv) into .agents/skills/tackle-issue in your project. Codex loads it when a task matches its description.

Can I use Tackle Issue 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 yamcodes/arkenv --skill tackle-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/tackle-issue, .gemini/skills/tackle-issue, .github/skills/tackle-issue and .opencode/skills/tackle-issue in your project.

What does Tackle Issue need to run?

Going by SKILL.md and its folder, Tackle Issue needs the command-line tools its instructions call (gh, pnpm and git).

Does Tackle Issue access the network?

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

Is Tackle Issue 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 Tackle Issue use?

Tackle Issue 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 Tackle Issue use?

About 1.1k tokens (SKILL.md is roughly 4.2k 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 Tackle Issue?

Skills that share tags, products or a category with Tackle Issue: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Merge Dependabot PRs (onyx-dot-app/onyx, 32k stars), Android UI Visual Review (permissionlesstech/bitchat-android, 7.7k stars) and Issue Fix (mono/SkiaSharp, 5.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tackle Issue?

yamcodes (a GitHub user) maintains it in yamcodes/arkenv, which has 145 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 5, 2026.

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