Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Batch Feature Dev · ledgerhq | DecimalAI

codingby ledgerhq

Batch Feature Dev

ledgerhq/batch-feature-dev

Source ledgerhq/ledger-live ↗License MIT

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

SkillScore82Maintained

Automatic

Coding pack

Last verified 8/16/2026

What it changes

Passed 18 of 22 test cases with the skill, and 15 of 22 without it.

Without skill68%

With skill82%

Checks it passed that the model alone missed

Independent ticket branches originate from updated develop.
UI implementation specifies using Lumen design system components.
Architecture guidance specifies loading mvvm-architecture prior to feature coding.

3 fixed15 passed either way4 still failing0 broke

Pass-rate lift: +14 pp
Tokens: -34%
Agent turns: 0%
Response time: -53%

Model gemini-3.6-flashMeasured 8/16/2026v118 of 22 cases passed with skill

Tokens, turns and time describe resource use, not a dollar price.

Use this skill

Save it into your project's skills folder. Claude Code picks it up in its next session.

curl -fsSL --create-dirs -o .claude/skills/ledgerhq-batch-feature-dev/SKILL.md https://app.decimal.ai/s/ledgerhq-batch-feature-dev/SKILL.md

Want it pinned and updatable? pip install "decimalai>=0.15", then decimalai skills add ledgerhq-batch-feature-dev, and start Claude Code with claude --plugin-dir "$(git rev-parse --show-toplevel)/.agents"

1 · One-time — install the CLI (docs ↗)

pip install "decimalai>=0.15"

2 · Get the skill — writes .agents/skills/ledgerhq-batch-feature-dev/ and pins it in .decimal/skills.lock

decimalai skills add ledgerhq-batch-feature-dev

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/ledgerhq-batch-feature-dev/SKILL.md https://app.decimal.ai/s/ledgerhq-batch-feature-dev/SKILL.md

Raw file: /s/ledgerhq-batch-feature-dev/SKILL.md ↗ · machine-readable summary at /s/ledgerhq-batch-feature-dev.json ↗

Safety checks: 3 of 3 passed

Code scan CleanIntent PassedContent Clean

See it in action

One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.

1 of 3

Prompt

I am about to write the domain and state management code for a wallet feature ticket. Before starting the feature implementation code, which architectural guidance skill should be loaded?

What was checked, without and with the skill
Checked	Without skill	With skill
Architecture guidance specifies loading mvvm-architecture prior to feature coding.	Missed	Passed

case-17 · gemini-3.6-flash · 8/16/2026 · answers are capped and redacted

What's inside

The instructions your model reads when the skill loads.

SKILL.md27 linessingle file

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

Intake every Jira ticket link, description, attachment, mockup, and constraint. Fetch details with available Jira/Atlassian tools; ask if anything is inaccessible.
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.
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.
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.
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.
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.

Track record

Benchmark

18 / 22

test cases passed, vs 15 / 22 without

Adoption

Users: 0
Times used: 0

Safety and source details

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 8/3/2026

View 15 scanner checks

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

ledgerhq / ledger-live

.agents/skills/batch-feature-dev/SKILL.md

View on GitHub ↗

License MITImported 8/3/2026Version v1

More skills from the same source and nearby in the registry, with their headline benchmark lift.

Ready to supercharge your AI agents?

See it in action

What's inside

Batch Feature Dev

Load First

Workflow

Stop When

Track record

Benchmark

Adoption

SkillSafety

Source

Related skills