batch-feature-dev

Coordinates batches of Jira tickets into scoped feature branches, changesets, and draft PRs.

615|491|Updated Jan 4, 2022
One-click install
npx skills add https://github.com/LedgerHQ/ledger-live --skill batch-feature-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: batch-feature-dev
Source: https://github.com/LedgerHQ/ledger-live/tree/main/.agents/skills/batch-feature-dev
Command: npx skills add https://github.com/LedgerHQ/ledger-live --skill batch-feature-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delivering multiple Jira tickets at once often leads to tangled branches, inconsistent validation, and unreviewable mega-PRs. This Skill orchestrates the full batch workflow so each ticket stays scoped, validated, and reviewable.

Core Features & Use Cases

  • Batch Intake & Planning: Fetches every Jira ticket's details, mockups, and constraints, then produces a dependency matrix covering UI impact, tests, shared work, and blockers before any code is written.
  • Branch & PR Orchestration: Applies git conventions for branching from develop, chains dependent tickets onto previous branches, and creates draft PRs with changesets for affected packages.
  • Guardrailed Feature Delivery: Enforces Lumen UI component usage, MVVM architecture, English-only source translations, and lint/test/typecheck validation per ticket.
  • Use Case: A developer receives five Jira tickets for a Ledger Wallet mobile release. The Skill analyzes all five, identifies two that share groundwork, creates a foundation PR plus dependent PRs, and hands off each with validation results and screenshots.

Quick Start

Ask the agent to process a list of Jira ticket links and deliver each one as a separate draft PR with changesets and validation results.

Frequently Asked Questions about batch-feature-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deliver multiple Jira tickets as separate PRs?

Provide all Jira ticket links at once so the batch workflow can build a dependency matrix, then run full feature development per ticket. Each ticket gets its own branch, changeset, validation, and draft PR with a handoff summary.

How should dependent tickets be branched in a monorepo?

Start unrelated tickets from an updated develop branch, and chain dependent tickets onto the previous ticket's branch, stating the target in the PR. For shared groundwork, prefer one small foundation PR plus dependent PRs.

Does this workflow support Lumen UI components?

Yes, the workflow loads Lumen UI guardrails (ldls-native or ldls-web) before any UI work and requires using Lumen components rather than custom ones. UI changes also require screenshots or manual visual checks during validation.

When does the batch workflow pause for human input?

It pauses when ticket or mockup details are missing, tickets conflict with each other, product or design decisions are needed, validation is meaningless, or the branch chaining strategy changes. Consolidated questions are asked before coding begins.

What validation runs before each draft PR is created?

Each ticket is validated with lint, relevant tests, typecheck, and screenshots or manual visual checks for UI changes. A changeset with exact package names is added before the draft PR and Slack message are created.