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

Batch Feature Dev

by LedgerHQ in LedgerHQ/ledger-live

Handle batches of Jira tickets through shared analysis, per-ticket feature-dev, Lumen UI guardrails, changesets, and draft PRs.

MITAuto-check passedAI & LLM Engineering

Install Batch Feature Dev

skills CLI
$ npx skills add LedgerHQ/ledger-live --skill batch-feature-dev -a claude-code

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

GitHub CLI
$ gh skill install LedgerHQ/ledger-live batch-feature-dev --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/LedgerHQ/ledger-live.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/batch-feature-dev .claude/skills/batch-feature-dev && 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
batch-feature-dev
GitHub stars
621
Token cost
~549 tokens
SKILL.md length
258 words
Files
1
Skills in repo
50
Repo updated
First seen
Licence
MIT

At a glance

Handle batches of Jira tickets through shared analysis, per-ticket feature-dev, Lumen UI guardrails, changesets, and draft PRs.

  • Works in 6 steps: Intake every Jira ticket link,… → Before coding, produce a compact matrix:… → Branch via git-conventions. Start… → …
  • The user provides multiple Jira tickets
  • SKILL.md covers Load First, Workflow and Stop When
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Batch Feature Dev is an agent skill from LedgerHQ/ledger-live. Handle batches of Jira tickets through shared analysis, per-ticket feature-dev, Lumen UI guardrails, changesets, and draft PRs. Use when the user provides multiple Jira tickets or asks to deliver tickets one by one with PRs.

Its SKILL.md is about 550 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 AI & LLM Engineering. It works with Jira. The repository describes itself as: Mono-repository for Ledger Wallet apps and related packages. The licence is MIT.

When your agent uses it

  • The user provides multiple Jira tickets
  • Asks to deliver tickets one by one with PRs

Example prompts

  • “/batch-feature-dev”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Intake every Jira ticket link, description, attachment, mockup, and constraint. Fetch details with available Jira/Atlassian tools; ask if…
  2. Before coding, produce a compact matrix: id/link, area, UI impact, tests/screenshots, dependencies, shared work, blockers. Ask…
  3. Branch via git-conventions. Start unrelated tickets from updated develop; chain only for real dependencies, target the previous branch…
  4. For each ticket/group, run full feature-dev. Treat tickets and mockups as source of truth; ask on conflicts; use Lumen components; add…
  5. Validate affected scope with lint, relevant tests, typecheck, and screenshots or manual visual checks for UI. Add a changeset with exact…
  6. Handoff each PR with ticket, branch, target, URL, changeset, validation results, screenshots/status, risks, and follow-ups. After the…

What it can do on your machine

Read from SKILL.md and the folder at commit a3861a2. 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

    No scripts in the folder and no shell commands in SKILL.md.

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

  • Network

    No URLs in SKILL.md.

    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

Batch Feature Dev loads about 549 tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 258 words of instructions outside code blocks.

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

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 LedgerHQ/ledger-live at commit a3861a2, republished under its MIT licence (© LedgerHQ). 258 words, ~549 tokens.

Download SKILL.mdSave it as .claude/skills/batch-feature-dev/SKILL.md (or your agent's skills folder).
name
batch-feature-dev
description
Handle batches of Jira tickets through shared analysis, per-ticket feature-dev, Lumen UI guardrails, changesets, and draft PRs. Use when the user provides multiple Jira tickets or asks to deliver tickets one by one with PRs.

Batch Feature Dev

Deliver ticket batches as coordinated PRs while keeping each ticket scoped and reviewable.

Load First

Read relevant skills before entering their phase:

  • feature-dev per ticket or coupled group.
  • git-conventions before branch, commit, rebase, or push work.
  • create-changeset before changesets; create-pr for draft PRs.
  • ldls-native or ldls-web before Lumen UI work.
  • mvvm-architecture before app feature code.
  • run-tests for validation.

Workflow

  1. Intake every Jira ticket link, description, attachment, mockup, and constraint. Fetch details with available Jira/Atlassian tools; ask if anything is inaccessible.
  2. Before coding, produce a compact matrix: id/link, area, UI impact, tests/screenshots, dependencies, shared work, blockers. Ask consolidated questions for missing mockups, conflicts, unclear copy, APIs, analytics, navigation, flags, and edge cases.
  3. Branch via git-conventions. Start unrelated tickets from updated develop; chain only for real dependencies, target the previous branch, and state it in the PR. For shared groundwork, prefer one small foundation PR plus dependent PRs.
  4. For each ticket/group, run full feature-dev. Treat tickets and mockups as source of truth; ask on conflicts; use Lumen components; add only English source translations; keep shared utilities owned and justified.
  5. Validate affected scope with lint, relevant tests, typecheck, and screenshots or manual visual checks for UI. Add a changeset with exact package names; use create-pr for draft PR and Slack message.
  6. Handoff each PR with ticket, branch, target, URL, changeset, validation results, screenshots/status, risks, and follow-ups. After the batch, summarize dependency graph and review order.

Stop When

Pause for missing ticket/mockup details, incompatible tickets, product/design decisions, meaningless validation, or changed chaining strategy.

© LedgerHQ, 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 .agents/skills/batch-feature-dev of LedgerHQ/ledger-live.

Open the folder on GitHubat commit a3861a2

Compare with similar skills

Batch Feature Dev 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.

Batch Feature Dev compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Batch Feature Dev this skillLedgerHQ/ledger-live621—~549Automated safety check: PassMIT
Codemie Assistant Buildercodemie-ai/codemie-code294—~3.3kAutomated safety check: PassApache-2.0
Project Opsericrisco/rsc-harness156—~2.4kAutomated safety check: PassMIT
Agent BuildershareAI-lab/learn-claude-code78k6 repos~1.2kAutomated safety check: PassMIT
Add Uint Supportpytorch/pytorch104k2 repos~2.3kAutomated safety check: PassCustom licence
Peft Fine TuningOrchestra-Research/AI-Research-SKILLs13k9 repos~3.1kAutomated safety check: PassMIT

Similar skills

  • Codemie Assistant Builder

    codemie-ai/codemie-code

    Build, test and autonomously improve CodeMie platform assistants.

    294 GitHub stars~3.3k tokensUpdated yesterday
    AI & LLM EngineeringAuto-check passed

  • Project Ops

    ericrisco/rsc-harness

    A skill your agent uses when an operator wants to run a small or mid-sized project from a flat file instead of standing up Jira or Asana — dated milestones each with one named owner and a binary…

    156 GitHub stars~2.4k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

  • Agent Builder

    shareAI-lab/learn-claude-code

    Design and build AI agents for any domain. An agent skill from shareAI-lab/learn-claude-code.

    78k GitHub starsUsed in 6 repos~1.2k tokens
    AI & LLM EngineeringAuto-check passed

  • Add Uint Support

    pytorch/pytorch

    Add unsigned integer (uint) type support to PyTorch operators by updating ATDISPATCH macros.

    104k GitHub starsUsed in 2 repos~2.3k tokens
    AI & LLM EngineeringAuto-check passed

  • Peft Fine Tuning

    Orchestra-Research/AI-Research-SKILLs

    Parameter-efficient fine-tuning for LLMs using LoRA, QLoRA, and 25+ methods.

    13k GitHub starsUsed in 9 repos~3.1k tokens
    AI & LLM EngineeringAuto-check passed

  • Segment Anything Model Guide

    Orchestra-Research/AI-Research-SKILLs

    Guide to using Meta's Segment Anything Model for zero-shot image segmentation with point, box or mask prompts, or automatic mask generation.

    13k GitHub starsUsed in 9 repos~3.3k tokens
    AI & LLM EngineeringAuto-check passed

More from LedgerHQ/ledger-live

All 50 skills in this repo

  • Impacting PRs

    LedgerHQ/ledger-live

    Find which open PRs are impacted by a migration/sunset/refactor and notify their authors — blocking review when the old path is already gone from develop, heads-up comment when it is only deprecated…

    621 GitHub stars~3.3k tokensUpdated today
    Auto-check passed

  • Cloud Sync Module

    LedgerHQ/ledger-live

    Write, review or debug a cloudSyncModule.ts — a CloudSyncDataManager that syncs one slice of user data through Ledger Sync (Cloud Sync).

    621 GitHub stars~2.4k tokensUpdated today
    Auto-check passed

  • Codeownership

    LedgerHQ/ledger-live

    Maintain CODEOWNERS file and team directories. An agent skill from LedgerHQ/ledger-live.

    621 GitHub stars~687 tokensUpdated today
    Auto-check passed

  • Coin Families Contract

    LedgerHQ/ledger-live

    Coin-specific families logic must live in families/. An agent skill from LedgerHQ/ledger-live.

    621 GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Data Layer Advanced

    LedgerHQ/ledger-live

    Structure a Ledger Wallet data layer where one API response serves several entities.

    621 GitHub stars~509 tokensUpdated today
    Auto-check passed

  • Debug Rn Native Crash

    LedgerHQ/ledger-live

    Investigate native React Native crashes (Fabric/Hermes/iOS) in ledger-live-mobile when JS error logs are missing or unhelpful.

    621 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Batch Feature Dev

What does Batch Feature Dev do?

Handle batches of Jira tickets through shared analysis, per-ticket feature-dev, Lumen UI guardrails, changesets, and draft PRs. Batch Feature Dev is an agent skill from LedgerHQ/ledger-live. Handle batches of Jira tickets through shared analysis, per-ticket feature-dev, Lumen UI guardrails, changesets, and draft PRs.

When should I use Batch Feature Dev?

Batch Feature Dev fits situations like: the user provides multiple Jira tickets; asks to deliver tickets one by one with PRs.

How do I install Batch Feature Dev in Claude Code?

Run `npx skills add LedgerHQ/ledger-live --skill batch-feature-dev -a claude-code`. Or copy the skill folder (.agents/skills/batch-feature-dev in LedgerHQ/ledger-live) into .claude/skills/batch-feature-dev in your project. Claude Code loads it when a task matches its description.

How do I install Batch Feature Dev in Codex?

Run `npx skills add LedgerHQ/ledger-live --skill batch-feature-dev -a codex`. Or copy the skill folder (.agents/skills/batch-feature-dev in LedgerHQ/ledger-live) into .agents/skills/batch-feature-dev in your project. Codex loads it when a task matches its description.

Can I use Batch Feature Dev 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 LedgerHQ/ledger-live --skill batch-feature-dev -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/batch-feature-dev, .gemini/skills/batch-feature-dev, .github/skills/batch-feature-dev and .opencode/skills/batch-feature-dev in your project.

What does Batch Feature Dev need to run?

SKILL.md names no scripts, command-line tools or credentials: Batch Feature Dev is instructions for the agent only.

Does Batch Feature Dev access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Batch Feature Dev 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 Batch Feature Dev use?

Batch Feature Dev 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 Batch Feature Dev use?

About 549 tokens (SKILL.md is roughly 2.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 Batch Feature Dev?

Skills that share tags, products or a category with Batch Feature Dev: Codemie Assistant Builder (codemie-ai/codemie-code, 294 stars), Project Ops (ericrisco/rsc-harness, 156 stars), Agent Builder (shareAI-lab/learn-claude-code, 78k stars) and Add Uint Support (pytorch/pytorch, 104k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Batch Feature Dev?

LedgerHQ (a GitHub organization) maintains it in LedgerHQ/ledger-live, which has 621 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 7, 2026.

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