How do I install the Add Locale Batch skill?

Run npx skillmds@latest add humanizr/add-locale-batch in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Add Locale Batch safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Add Locale Batch?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Add Locale Batch free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Add Locale Batch?

humanizr (@humanizr) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Add Locale Batch by humanizr — Agent Skill

Name: Add Locale Batch
Author: humanizr

Add Locale Batch

Use when coordinating multiple Humanizer locale parity efforts across isolated worktrees, branches, PRs, review/CI babysitting, merges, and cleanup. This is the parent orchestration skill for locale batches; delegate each individual locale to add-locale rather than implementing locale details directly.

humanizr ca95c46 6 files · 10.9 KB Updated Sep 17, 2026

File contents

Humanizer Locale Batch Orchestration

Use this for multi-locale Humanizer parity work. It is a parent orchestration skill: each locale subagent still uses $add-locale for implementation and proof.

Non-negotiables

Parent coordinates only: plan, dispatch, track, verify, merge, cleanup.
One isolated sibling worktree and branch per locale; no child may edit main or a sibling worktree.
Each locale orchestrator must read $add-locale and set its own goal from .agents/skills/add-locale/references/goal-template.md.
Do not use draft PRs unless the user changes policy.
Merge only when every gate in references/pr-gates.md passes.
If multiple locales need the same generator/runtime/schema change, hold them and land one shared PR first; see references/batch-state.md.
After merge, clean the worktree/branches as described in references/pr-gates.md.
Never commit artifacts containing full local filesystem paths.

Workflow

Load or create batch state (references/batch-state.md).
Create one worktree/branch per active locale.
Dispatch locale orchestrators with references/locale-orchestrator-contract.md.
Poll with scripts/locale_batch_status.py; update phases; wake children only for deltas.
Hold new locales when asked; keep closing already-active PRs unless told otherwise.
Final rollup: locale, PR, merge commit, validation, babysit result, cleanup, deferred locales.

Compact dispatch

Read .agents/skills/add-locale-batch/references/locale-orchestrator-contract.md.
Locale: <code> / <name>.
Worktree: <relative-path>. Branch: <branch>. PR: <number-or-new>.
Phase: <batch-state phase>. Known blockers: <none|summary>.
Report compact JSON status only unless blocked.

References

references/batch-state.md — plan/status schema, phases, shared-change hold flow.
references/locale-orchestrator-contract.md — child-agent contract.
references/pr-gates.md — PR polling, merge gate, cleanup.

---name: add-locale-batchdescription: Use when coordinating multiple Humanizer locale parity efforts across isolated worktrees, branches, PRs, review/CI babysitting, merges, and cleanup. This is the parent orchestration skill for locale batches; delegate each individual locale to add-locale rather than implementing locale details directly.---# Humanizer Locale Batch OrchestrationUse this for multi-locale Humanizer parity work. It is a parent orchestration skill: each locale subagent still uses `$add-locale` for implementation and proof.## Non-negotiables- Parent coordinates only: plan, dispatch, track, verify, merge, cleanup.- One isolated sibling worktree and branch per locale; no child may edit main or a sibling worktree.- Each locale orchestrator must read `$add-locale` and set its own goal from `.agents/skills/add-locale/references/goal-template.md`.- Do not use draft PRs unless the user changes policy.- Merge only when every gate in `references/pr-gates.md` passes.- If multiple locales need the same generator/runtime/schema change, hold them and land one shared PR first; see `references/batch-state.md`.- After merge, clean the worktree/branches as described in `references/pr-gates.md`.- Never commit artifacts containing full local filesystem paths.## Workflow1. Load or create batch state (`references/batch-state.md`).2. Create one worktree/branch per active locale.3. Dispatch locale orchestrators with `references/locale-orchestrator-contract.md`.4. Poll with `scripts/locale_batch_status.py`; update phases; wake children only for deltas.5. Hold new locales when asked; keep closing already-active PRs unless told otherwise.6. Final rollup: locale, PR, merge commit, validation, babysit result, cleanup, deferred locales.## Compact dispatch```textRead .agents/skills/add-locale-batch/references/locale-orchestrator-contract.md.Locale: <code> / <name>.Worktree: <relative-path>. Branch: <branch>. PR: <number-or-new>.Phase: <batch-state phase>. Known blockers: <none|summary>.Report compact JSON status only unless blocked.```## References- `references/batch-state.md` — plan/status schema, phases, shared-change hold flow.- `references/locale-orchestrator-contract.md` — child-agent contract.- `references/pr-gates.md` — PR polling, merge gate, cleanup.

Frequently asked questions