codyswanngt/linear-verify
plugins/lisa-cursor/skills/linear-verify/SKILL.md
Verifies a Linear work item meets organizational standards by fetching the live item and running it through lisa:linear-validate-issue. Catches anything dropped or reformatted on write — same gates as the pre-write check, but applied to what Linear actually stored. Read-only.
$ install --global
skillsauthnpx skillsauth add codyswanngt/lisa linear-verifyInstall 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 31, 2026, 3:46 AM53.5s1 file scanned
SKILL.md
- name:
- linear-verify
- description:
- Verifies a Linear work item meets organizational standards by fetching the live item and running it through lisa:linear-validate-issue. Catches anything dropped or reformatted on write — same gates as the pre-write check, but applied to what Linear actually stored. Read-only.
- allowed-tools:
- ["Bash", "Skill", "mcp__linear-server__list_teams", "mcp__linear-server__get_issue", "mcp__linear-server__get_project", "mcp__linear-server__list_issue_labels", "mcp__linear-server__list_project_labels"]
Verify Linear Work Item: $ARGUMENTS
Fetch the live Linear work item and run it through lisa:linear-validate-issue. This catches any field that was dropped or reformatted between the pre-write spec and what Linear stored.
This skill is the destination of the lisa:tracker-verify shim when tracker = "linear". Read-only — never writes.
Configuration
Reads linear.workspace, linear.teamKey from .lisa.config.json (with .local override).
Input
$ARGUMENTS is a Linear identifier:
- An Issue identifier (e.g.
ENG-123) - A Project URL or slug (e.g.
https://linear.app/<workspace>/project/<slug>-<id>)
If $ARGUMENTS is not parseable, stop and report.
Phase 1 — Resolve Context
- Read
linear.workspace,linear.teamKeyfrom.lisa.config.json(with.localoverride). - Resolve team ID via
mcp__linear-server__list_teams({query: <teamKey>}). - Determine entity type from the identifier shape:
<TEAM>-<n>→ Issue- URL containing
/project/<slug>-<id>→ Project
Phase 2 — Fetch Live State
Call mcp__linear-server__get_issue (for Issues) or mcp__linear-server__get_project (for Projects). Capture every field, label, relation, comment, milestone, and project membership.
Phase 3 — Delegate to Validator
Pass the fetched item to lisa:linear-validate-issue (in identifier mode — let it derive the spec from the live state). The validator runs both Specification AND Feasibility gates against what Linear actually stored.
Phase 4 — Report
Return the validator's report verbatim — same structured format as lisa:linear-validate-issue. Callers (especially lisa:linear-write-issue Phase 7) parse the verdict to decide whether to declare success.
If the verdict is FAIL, the caller should fix the item and re-run verify. Never declare success on a FAIL verdict.
Rules
- Never write to Linear. Read-only.
- Never short-circuit the validator. Always run the full gate set.
- If
get_issue/get_projectreturns an access error, surface it and exit — don't pretend the item is fine.
Related Skills
codyswanngt/lisa-wiki-onboard-me
documentation
VerifiedTrustedCommunity
Onboard a user to the project via its LLM Wiki. Interviews the user about themselves in relation to the project, captures that to project-scoped memory only, then gives a guided tour of what the project is and sample questions they can ask. Use when someone is new to the project or asks to be onboarded. Read-mostly — it does not open PRs or write PII into the wiki.
1SKILL.mdUpdated Jun 5, 2026
codyswanngt/lisa-wiki-migrate
documentation
VerifiedTrustedCommunity
Migrate an existing, hand-rolled wiki implementation onto the lisa-wiki kernel — phased and compatibility-first, with a strict no-loss guarantee. Use when adopting lisa-wiki in a repo that already has its own wiki/, ingest skills, docs, or roles. Renaming things into the canonical shape is fine; losing functionality or data is not. Ends by running /doctor.
1SKILL.mdUpdated Jun 5, 2026
codyswanngt/lisa-wiki-lint
development
VerifiedTrustedCommunity
Health-check the LLM Wiki. Reports orphan pages, contradictions, stale claims, broken internal links, missing index/log coverage, structure-manifest violations, and secret/tenant leaks. Use periodically or before hardening a wiki. Read-only — it reports findings, it does not fix them.
1SKILL.mdUpdated Jun 5, 2026
codyswanngt/lisa-wiki-ingest
testing
VerifiedTrustedCommunity
Ingest source material into the LLM Wiki. With an argument (URL, file path, or prompt) it ingests that one source; with no argument it runs a full ingest across every enabled non-external-write source. Routes to the right connector, then runs the ordered pipeline (source note → synthesis → index → log → verify → state → commit/PR). Use whenever new knowledge should enter the wiki.
1SKILL.mdUpdated Jun 5, 2026