linear-issue-delivery
Keep a Linear issue aligned with implementation evidence, acceptance criteria, code review, and deployment state while avoiding premature completion claims.
git clone --depth 1 https://github.com/Devin-AXIS/iPolloWork /tmp/linear-issue-delivery && cp -r /tmp/linear-issue-delivery/examples/plugin-packages/linear/skills/linear-issue-delivery ~/.claude/skills/linear-issue-deliverySKILL.md
# Linear Issue Delivery 1. Read the issue, linked work, acceptance criteria, and current status. 2. Inspect the local or remote implementation evidence supplied by the user. 3. Report gaps between the issue and the actual change before editing either side. 4. Add concise evidence or update status only when the requested milestone is genuinely reached. 5. Preserve links to pull requests, tests, releases, or follow-up issues when available. Do not mark work done based only on a local edit. Distinguish local implementation, pushed code, merged code, and deployed behavior.
Search and summarize material from the Acme research service.
Agent-first screenshots — an agent drives the real app via CDP and produces clean, defect-free product screenshots (newsletters, landing pages, social, decks, PR). Dual-channel verification (DOM + pixels + vision) in a capture loop. Use for any "take/redo screenshots of the app" task.
Resolve the correct library and retrieve a small, relevant set of version-aware official documentation before answering a technical question.
Use the current project dependency versions and Context7 documentation to implement or upgrade code without importing APIs from a different release line.
Create an OpenCode plugin for iPolloWork. Scaffolds the plugin file with the correct API shape, tool definitions, and hook registration. Use when the user asks to 'create a plugin', 'write a plugin', or 'make a plugin that does X'.
Launch and control standalone Chrome in a Daytona sandbox via CDP. Use for web sign-in, OAuth, Den Web setup, browser-only flows, or when the app should not be driven through Electron CDP.
Daytona cloud server, Den sandbox, desktop plus cloud e2e, marketplace server, worker proxy, cloud auth, org policies, connect Electron to Den. Use for server-side setup in validated flows.
Daytona development environment overview. Use when the user asks about Daytona setup, Daytona toolbox, dev environment, noVNC, CDP, server sandbox, secrets volume, Electron sandbox, standalone Chrome, validation, or artifacts volume.