lemessdavi/linear-delivery-sync
skills/linear-delivery-sync/SKILL.md
Use the Linear MCP from the scaffolded Linear link to align implementation with issues/projects, suggest card updates, and keep Linear documentation in sync.
tools
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add lemessdavi/ia-prev linear-delivery-syncInstall 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: Apr 16, 2026, 5:34 PM7.9s1 file scanned
SKILL.md
- name:
- linear-delivery-sync
- description:
- Use the Linear MCP from the scaffolded Linear link to align implementation with issues/projects, suggest card updates, and keep Linear documentation in sync.
Linear Delivery Sync
Goal
Use Linear as the operational source of truth while coding.
Inputs
- Canonical Linear URL in
.project-context/linear.md. - Current task scope from code changes and tests.
Workflow
- Read
.project-context/linear.md. - Parse URL type:
.../issue/<KEY>-> fetch issue details and comments..../project/...-> fetch project and relevant open issues.
- Align current implementation scope with Linear item status.
- Suggest concise progress messages for the active card.
- Suggest documentation updates in Linear when architecture/workflow changed.
MCP Usage Guidelines
- Prefer issue-specific APIs for issue links.
- Prefer project + issue listing APIs for project links.
- Keep updates factual: what changed, tests run, risks/next steps.
- Do not change state/assignee unless explicitly requested.
Suggested Card Message Template
Implemented:
- <what changed>
Validation:
- <tests and gates run>
Notes:
- <risk, follow-up, docs touched>
Related Skills
lemessdavi/xp-delivery-loop
testing
VerifiedTrustedCommunity
Use for every implementation task in this template. Enforces pair-programming with AI, small releases, and continuous integration discipline.
SKILL.mdUpdated Apr 16, 2026
lemessdavi/test-driven-development
development
VerifiedTrustedCommunity
Use before any feature, bugfix, or behavior change. Write failing tests first, then implement minimum code.
SKILL.mdUpdated Apr 16, 2026
lemessdavi/refactor-continuous
development
VerifiedTrustedCommunity
Use after green tests to keep codebase healthy through small and frequent refactors instead of large rescue rewrites.
SKILL.mdUpdated Apr 16, 2026
lemessdavi/docs-living-spec
testing
VerifiedTrustedCommunity
Keep CLAUDE.md and AGENTS.md aligned with reality. Use when new decisions, hurdles, or patterns emerge during implementation.
SKILL.mdUpdated Apr 16, 2026