| name | lisa-tracker-validate |
| description | Vendor-neutral wrapper for the pre-write quality gate. Reads the required `tracker` from .lisa.config.json and dispatches to lisa-jira-validate-ticket, lisa-github-validate-issue, or lisa-linear-validate-issue. Read-only — never writes to any tracker. Used by tracker-write Phase 5.5 (pre-write gate), tracker-verify (post-write checks), and the *-to-tracker dry-run paths. Output is structured PASS/FAIL per gate so callers can parse it. |
| allowed-tools | ["Skill","Bash","Read"] |
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
-
Resolve tracker config (same logic as lisa-tracker-write Step 1):
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}"
-
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'."
-
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.
