# Lisa Tracker Validate

> Vendor-neutral wrapper for the…

- Skill: `codyswanngt/lisa-tracker-validate` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add codyswanngt/lisa-tracker-validate`
- Raw SKILL.md: https://api.skillmd.com/api/skills/codyswanngt/lisa-tracker-validate/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: codyswanngt (https://skillmd.com/u/codyswanngt)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/codyswanngt/lisa-tracker-validate

---


# Tracker Validate: $ARGUMENTS

Thin dispatcher. Resolves the configured destination tracker and delegates to the matching vendor validator.

See the `config-resolution` rule for the full configuration schema and skill-mapping table.

## Workflow

1. **Resolve tracker config** (same logic as `lisa-tracker-write` Step 1):

   ```bash
   local_tracker=$(jq -r '.tracker // empty' .lisa.config.local.json 2>/dev/null)
   global_tracker=$(jq -r '.tracker // empty' .lisa.config.json 2>/dev/null)
   tracker="${local_tracker:-$global_tracker}"
   ```

2. **Dispatch**

   - Missing / empty → stop and report `"No tracker configured in .lisa.config.json. Run /lisa:setup:jira, /lisa:setup:github, or /lisa:setup:linear first."`
   - `jira` → invoke `lisa-jira-validate-ticket` with `$ARGUMENTS` verbatim.
   - `github` → invoke `lisa-github-validate-issue` with `$ARGUMENTS` verbatim.
   - `linear` → invoke `lisa-linear-validate-issue` with `$ARGUMENTS` verbatim.
   - Anything else → stop and report `"Unknown tracker '<value>' in .lisa.config.json. Expected 'jira', 'github', or 'linear'."`

3. **Pass through the validator's structured report unchanged.** Callers (e.g. `lisa-jira-write-ticket` Phase 5.5) parse the gate lines; do not paraphrase.

## Rules

- Read-only — never write to any tracker.
- Never re-implement gate logic here. The gate definitions are the vendor validator's responsibility.
- Never silently transform the input — pass `$ARGUMENTS` through verbatim.