How do I install the Validate Branch skill?

Run npx skillmds@latest add getlark/validate-branch 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 Validate Branch 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 Validate Branch?

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 Validate Branch free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Validate Branch?

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

Validate Branch by getlark — Agent Skill

Name: Validate Branch
Author: getlark

Validate Branch

This skill should be used when the user asks to "validate the branch", "validate this branch", "test this feature branch", "run workflows against this branch", "check if my changes broke anything", or runs `/getlark:validate-branch`. Runs configured getlark workflows against the current branch on demand. Pair with the optional PostToolUse hook for automatic validation after git commit/push. Prefer this over `invoke-workflow` whenever the intent is tied to the current git branch — it selects the right workflows automatically from `.claude/getlark.local.md`; fall back to `invoke-workflow` for ad-hoc runs unrelated to the branch, and to `create-workflow` if no workflows exist yet.

getlark 2872913 3.3 KB Updated Sep 17, 2026

File contents

validate-branch

Run getlark workflows to validate the work-in-progress on the current git branch, on demand. Reads optional configuration from .claude/getlark.local.md if present, otherwise runs all workflows (the sensible default for onboarding).

Procedure

Step 1 — Identify current branch

git rev-parse --abbrev-ref HEAD

Abort with a clear message if not in a git repo or HEAD is detached — unless the user explicitly opted into running anyway.

Step 2 — Load project config (if present)

Look for .claude/getlark.local.md in $CLAUDE_PROJECT_DIR (or pwd fallback). If it exists, parse the YAML frontmatter:

---
enabled: true
workflow_ids: []            # empty = all workflows
workflow_group_id: ""       # alternative to workflow_ids
poll_timeout_seconds: 600
---

Use Read to inspect it. Settings precedence, when multiple are set:

workflow_ids (if non-empty)
workflow_group_id (if non-empty)
Otherwise run --all

If the file is missing, default to --all.

Step 3 — Override from skill argument

If the user passed an argument to /getlark:validate-branch:

wf_... → single workflow via --workflow-ids
Group name → --group-name "<name>"
Any other token → ask the user to clarify

The argument wins over the config file.

Step 4 — Invoke

Always wait for completion. Use the configured timeout or 600s default.

getlark workflows invoke --all --wait --timeout <seconds>
# or
getlark workflows invoke --workflow-ids <ids...> --wait --timeout <seconds>
# or
getlark workflows invoke --group-id <id> --wait --timeout <seconds>

Step 5 — Report

Follow the same result-interpretation rules as /getlark:invoke-workflow:

Exit 0 → ✅ branch passes
Exit 1 → list failing workflows + dashboard links
Exit 2 → timeout
Exit 3 → unexpected error

Include the current branch name in the summary so the user sees e.g. "Branch feature/checkout-v2 passed all 12 workflows."

Relationship to the hook

This plugin ships an opt-in PostToolUse hook that runs this same validation automatically after git commit or git push. It uses the same .claude/getlark.local.md config. Enable it by setting enabled: true in that file. When disabled or missing, the hook is a no-op.

Users can always run /getlark:validate-branch manually regardless of hook state.

Do NOT

Do not guess the CLI command format; reuse the same flags as /getlark:invoke-workflow.
Do not run on main / master / the repo's default branch unless the user explicitly asks (the purpose is feature-branch validation).

---name: validate-branchdescription: This skill should be used when the user asks to "validate the branch", "validate this branch", "test this feature branch", "run workflows against this branch", "check if my changes broke anything", or runs `/getlark:validate-branch`. Runs configured getlark workflows against the current branch on demand. Pair with the optional PostToolUse hook for automatic validation after git commit/push. Prefer this over `invoke-workflow` whenever the intent is tied to the current git branch — it selects the right workflows automatically from `.claude/getlark.local.md`; fall back to `invoke-workflow` for ad-hoc runs unrelated to the branch, and to `create-workflow` if no workflows exist yet.license: MIT---# validate-branchRun getlark workflows to validate the work-in-progress on the current git branch, on demand. Reads optional configuration from `.claude/getlark.local.md` if present, otherwise runs **all** workflows (the sensible default for onboarding).## Procedure### Step 1 — Identify current branch```bashgit rev-parse --abbrev-ref HEAD```Abort with a clear message if not in a git repo or HEAD is detached — unless the user explicitly opted into running anyway.### Step 2 — Load project config (if present)Look for `.claude/getlark.local.md` in `$CLAUDE_PROJECT_DIR` (or `pwd` fallback). If it exists, parse the YAML frontmatter:```yaml---enabled: trueworkflow_ids: [] # empty = all workflowsworkflow_group_id: "" # alternative to workflow_idspoll_timeout_seconds: 600---```Use Read to inspect it. Settings precedence, when multiple are set:1. `workflow_ids` (if non-empty)2. `workflow_group_id` (if non-empty)3. Otherwise run `--all`If the file is missing, default to `--all`.### Step 3 — Override from skill argumentIf the user passed an argument to `/getlark:validate-branch`:- `wf_...` → single workflow via `--workflow-ids`- Group name → `--group-name "<name>"`- Any other token → ask the user to clarifyThe argument wins over the config file.### Step 4 — InvokeAlways wait for completion. Use the configured timeout or 600s default.```bashgetlark workflows invoke --all --wait --timeout <seconds># orgetlark workflows invoke --workflow-ids <ids...> --wait --timeout <seconds># orgetlark workflows invoke --group-id <id> --wait --timeout <seconds>```### Step 5 — ReportFollow the same result-interpretation rules as `/getlark:invoke-workflow`:- Exit 0 → ✅ branch passes- Exit 1 → list failing workflows + dashboard links- Exit 2 → timeout- Exit 3 → unexpected errorInclude the current branch name in the summary so the user sees e.g. "Branch `feature/checkout-v2` passed all 12 workflows."## Relationship to the hookThis plugin ships an opt-in `PostToolUse` hook that runs this same validation automatically after `git commit` or `git push`. It uses the same `.claude/getlark.local.md` config. Enable it by setting `enabled: true` in that file. When disabled or missing, the hook is a no-op.Users can always run `/getlark:validate-branch` manually regardless of hook state.## Do NOT- Do not guess the CLI command format; reuse the same flags as `/getlark:invoke-workflow`.- Do not run on `main` / `master` / the repo's default branch unless the user explicitly asks (the purpose is feature-branch validation).

Frequently asked questions