codyswanngt/jira-journey
plugins/src/base/skills/jira-journey/SKILL.md
Parse a JIRA ticket's Validation Journey section, execute the verification steps using appropriate tools (curl, test commands, database queries), capture evidence, and post to JIRA + GitHub PR using the jira-evidence skill.
$ install --global
skillsauthnpx skillsauth add codyswanngt/lisa jira-journeyInstall 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: May 23, 2026, 4:06 AM108.3s3 files scanned
SKILL.md
- name:
- jira-journey
- description:
- Parse a JIRA ticket's Validation Journey section, execute the verification steps using appropriate tools (curl, test commands, database queries), capture evidence, and post to JIRA + GitHub PR using the jira-evidence skill.
- allowed-tools:
- ["Bash", "Read", "Glob", "Grep", "Skill"]
JIRA Validation Journey (TypeScript)
All Atlassian operations in this skill go through lisa:atlassian-access. Do not call MCP tools or acli directly. Note: the helper scripts (scripts/parse-plan.py, scripts/jira-evidence/post-evidence.sh) currently use direct API calls and are pending migration to route through atlassian-access.
Parse a JIRA ticket's Validation Journey, execute the verification steps using the appropriate tools for the change type, capture evidence at each [EVIDENCE: name] marker, and post to JIRA + GitHub PR.
Arguments
$ARGUMENTS: <TICKET_ID> [PR_NUMBER]
TICKET_ID(required): JIRA ticket key (e.g.,PROJ-123)PR_NUMBER(optional): GitHub PR number to update description
Prerequisites
JIRA_API_TOKENenvironment variable setjira-cliconfigured (~/.config/.jira/.config.yml)ghCLI authenticated- Appropriate services running for the verification type (dev server, database, etc.)
Workflow
Step 1: Parse the Validation Journey
Run the parser script to extract the Validation Journey from the JIRA ticket description:
python3 .claude/skills/jira-journey/scripts/parse-plan.py <TICKET_ID>
The script outputs JSON with: ticket, prerequisites, steps, viewports, assertions.
Note: viewports may be empty for TypeScript tickets — that is expected.
Step 2: Satisfy Prerequisites
Before starting the journey, verify each prerequisite:
- Check if required services are running
- Verify database connectivity if needed
- Ensure environment variables are set
- Run any setup commands mentioned in prerequisites
Step 3: Execute Steps and Capture Evidence
Execute each step sequentially. For each step, determine the verification approach based on the step text and change type:
- API endpoints → Run curl commands, capture HTTP response to
evidence/NN-name.txt - Database changes → Run psql/migration commands, capture schema output to
evidence/NN-name.txt - Background jobs → Trigger the job, check queue/state, capture logs to
evidence/NN-name.txt - Library/utility changes → Run tests, capture output to
evidence/NN-name.txt - Security fixes → Reproduce exploit attempt, verify fix, capture output to
evidence/NN-name.txt
At each [EVIDENCE: name] marker, capture stdout/stderr to a numbered file:
Evidence Naming Convention
Evidence files are named: {NN}-{evidence-name}.txt (or .json for structured data)
NN: zero-padded sequential number (01, 02, 03...)evidence-name: the value from[EVIDENCE: name]in the JIRA step
Example:
evidence/
01-health-check.json
02-schema-after-migration.txt
03-rate-limit-response.txt
comment.txt
comment.md
Step 4: Generate Evidence Templates
After capturing all evidence, run the template generator:
python3 .claude/skills/jira-journey/scripts/generate-templates.py \
<TICKET_ID> \
<PR_NUMBER> \
<BRANCH_NAME> \
./evidence
This generates evidence/comment.txt (JIRA wiki markup) and evidence/comment.md (GitHub markdown) with evidence formatted as code blocks.
Step 5: Post Evidence
Use the jira-evidence skill to post everything:
bash .claude/skills/jira-evidence/scripts/post-evidence.sh <TICKET_ID> ./evidence <PR_NUMBER>
Step 6: Verify
Confirm evidence is posted to both the JIRA ticket and GitHub PR.
Verification Patterns Reference
The agent should use patterns from the project's verfication.md when executing steps:
| Change Type | Verification Method | Evidence Format |
|---|---|---|
| API endpoint | curl -s localhost:PORT/endpoint | JSON response |
| Database migration | psql -c "\d table" or migration output | Schema text |
| Background job | Trigger + check state | Log output |
| Library/utility | bun run test -- path/to/test | Test output |
| Security fix | Reproduce + verify fix | Request/response |
| Auth/authz | Multi-role verification | Status codes per role |
Troubleshooting
Evidence file is empty
Ensure the command succeeded and produced output. Use 2>&1 to capture both stdout and stderr.
Parser returns no steps
The ticket may not have a Validation Journey section. Use /jira-add-journey <TICKET_ID> to add one.
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