Agent skill · software engineering · jeremylongshore
linear-local-dev-loop
Build a fast Linear integration development loop using fixtures, contract boundaries, and an isolated test workspace. Use when iterating locally without polluting production Linear data. Trigger with "develop Linear locally", "mock Linear GraphQL", or "test Linear webhooks locally".
Why this skill is useful
Adds executable scripts for setting up a local Linear development environment, including project scaffolding and testing utilities that aren't in public docs.
What it needs
Requires node installed locally. Requires linear account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Linear Local Development Loop Overview Keep routine tests deterministic and offline, then use a deliberate read-only or sandbox-workspace probe to detect contract drift. Prerequisites The target repository, Linear workspace, environment, and accountable owner Current security, privacy, compliance, capacity, and change-control requirements An approved Linear credential only when a bounded live verification is necessary Tool Discipline Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current first-party Linear documentation and package metadata. Use Write or Edit only for requested implementation with known target files. Never write credentials, customer content, unrestricted environment output, or unredacted GraphQL variables. Current Contract Webhook delivery requires a publicly accessible HTTPS, non-localhost URL; localhost-only receivers are not a production-equivalent test. Signature verification requires the exact raw request body, so body-parser ordering belongs in local contract tests. GraphQL introspection and official generated SDK types are better schema authorities than hand-written guessed fixtures. Authentication Use a personal API key only for owner-controlled scripts, OAuth with PKCE for user-delegated applications, or an enabled client-credentials grant for approved automation. Personal keys use Authorization: <APIKEY>; OAuth tokens use Authorization: Bearer <ACCESSTOKEN>. Store credentials server-side in an approved secret manager. Treat app approval, team access, scope changes, credential creation, rotation, revocation, and production access as owner-approved actions. Instructions 1. Inspect the repository's test framework, GraphQL client boundary, fixtures, environment loading, and webhook middleware order. 2. Record minimal redacted success, partial-error, auth-error, throttling, pagination, and webhook fixtures. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/linear-local-dev-loop