codyswanngt/lisa-tracker-create
plugins/lisa/skills/lisa-tracker-create/SKILL.md
Vendor-neutral wrapper for creating tickets/issues from code files or descriptions. Reads the required `tracker` from .lisa.config.json and dispatches to lisa-jira-create, lisa-github-create, or lisa-linear-create. Plans hierarchy structure (epic / story / sub-task), then delegates each individual write through the tracker-write shim.
$ install --global
skillsauthnpx skillsauth add codyswanngt/lisa lisa-tracker-createInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Aug 30, 2026, 3:43 AM142.8s2 files scanned
SKILL.md
- name:
- lisa-tracker-create
- description:
- Vendor-neutral wrapper for creating tickets/issues from code files or descriptions. Reads the required `tracker` from .lisa.config.json and dispatches to lisa-jira-create, lisa-github-create, or lisa-linear-create. Plans hierarchy structure (epic / story / sub-task), then delegates each individual write through the tracker-write shim.
- allowed-tools:
- ["Skill", "Bash", "Read"]
Tracker Create: $ARGUMENTS
Thin dispatcher. Resolves the configured destination tracker and delegates to the matching vendor planning skill.
See the config-resolution rule for configuration and dispatch table.
Workflow
- Resolve tracker config (same logic as
lisa-tracker-write). - 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→ invokelisa-jira-createwith$ARGUMENTSverbatim.github→ invokelisa-github-createwith$ARGUMENTSverbatim.linear→ invokelisa-linear-createwith$ARGUMENTSverbatim.- Anything else → stop and report
"Unknown tracker '<value>' in .lisa.config.json. Expected 'jira', 'github', or 'linear'."
- Missing / empty → stop and report
- Pass through the output.
Rules
- All vendor skills delegate every individual ticket write through
lisa-tracker-write. They never call vendor-specific write tools directly. - Declare readiness on every leaf write. Per the
ready-role-filingrule an omittedbuild_readyis not build-ready on any tracker, so passbuild_ready: trueon each Sub-task (the leaf work units this skill plans) and never on the Epic or Stories, which are containers perleaf-only-lifecycle. A leaf that is deliberately held instead passeshuman_gate: "<why a human must judge this first>". Filing a leaf with neither is an incomplete handoff andlisa-tracker-writerejects it. - This shim is for ad-hoc creation from code files / descriptions. PRD-driven creation goes through the
*-to-trackerskills (notion / confluence / linear / github).
Related Skills
codyswanngt/lisa-setup-workstation
development
VerifiedTrustedCommunity
Prepare a machine — a fresh laptop or a throwaway container — to run coding agents, before any repository exists. Detects which of Lisa's supported agents (Claude Code, Codex, Cursor, OpenCode, Antigravity, Copilot) are already installed, asks which credential manager the machine uses (Bitwarden, 1Password, Doppler, Vault, AWS, or none), and installs only what is missing, each by its vendor's own preferred method. Idempotent, headless by default, and emits a Dockerfile for a spin-up/spin-down environment. Run it on a new machine, in a container, or before cloning anything.
3SKILL.mdUpdated Aug 30, 2026
codyswanngt/lisa-setup-remote-env
tools
VerifiedTrustedCommunity
Provision and verify a remote execution environment for a host project — Codex Cloud today, other remote surfaces as they are added. Generates a repository-owned setup script that installs the declared toolchain, materializes secrets through lisa-secrets-access, and runs the project's own hook. Provisions by API where one exists, by driving the vendor console where one does not, and by emitting exact config otherwise — then proves the result with the same read-back regardless of which tier did the work. Use before dispatching any work with executionEnv.
3SKILL.mdUpdated Aug 30, 2026
codyswanngt/lisa-setup-local-env
tools
VerifiedTrustedCommunity
Bring a developer's machine in line with the toolchain the project declares. Reports every tool in remoteEnv.tools that is missing, outdated, or unpinned for this platform, and installs the missing ones into ~/.local/bin from the same pinned, checksummed entries the remote surfaces use — but only when asked. Same manifest, same pins, same installers as lisa-setup-remote-env; what differs is consent and that the pin is a floor rather than an equality. Run it on a fresh checkout, after a manifest change, or when a tool fails at the moment of use.
3SKILL.mdUpdated Aug 30, 2026
codyswanngt/lisa-remote-dispatch
tools
VerifiedTrustedCommunity
Route one unit of work to a remote execution surface. Reads the executionEnv parameter (local by default, codex-cloud or claude-web today), verifies the environment is provisioned and bound to this repository, submits a thin skill invocation, records the task identifier to .lisa/remote-dispatch.json, and exits without polling. Routing only — the remote runs the identical skill from the identical repository. Composable and inline: other skills invoke it via the Skill tool rather than users calling it directly.
3SKILL.mdUpdated Aug 30, 2026