camwest/isq
Overview
This skill provides instant, offline-first issue management across GitHub, Linear, and JIRA using the isq CLI. It lets you list, create, comment, assign, and transition issues with sub-millisecond reads from a local SQLite cache. It also integrates with git worktrees so each issue can map to a dedicated branch and worktree for a seamless development context. Background sync keeps the local cache fresh and write operations queue when offline.
How this skill works
isq syncs remote issues into a local SQLite database so all reads are served instantly from disk and never require a network round-trip. Writes (creates, comments, state changes) are sent to the remote API when online or queued locally and synced by a background daemon when connectivity returns. The tool integrates with git worktrees: isq start <id> creates a worktree and branch, marks the issue in-progress, and attaches the issue to that worktree for automatic commit references and cleanup.
When to use it
- You want instant issue queries without API rate limits or slow network calls.
- You plan to work offline or on intermittent connectivity and need queued writes.
- You want each issue to have its own git worktree and automated branch handling.
- You need a machine-readable CLI interface for scripts or AI agent automation (--json).
- You want to manage GitHub, Linear, or JIRA issues from a consistent local workflow.
Best practices
- Link the repository with isq link before doing issue workflows to install the commit hook.
- Use isq start <id> to create worktrees and branches instead of creating branches manually.
- Run the daemon (isq daemon start) for continuous background sync and sub-millisecond reads.
- Use --json for scripts and automation to get stable machine-readable output.
- Keep views for common filters (isq view create) to save repetitive flags and standardize queries.
Example use cases
- Run isq issue list @my-bugs --json in a CI job to generate a JSON report of high-priority assigned bugs.
- Start working on issue 891 with isq start 891 to create a worktree, branch, and mark the issue in-progress automatically.
- Create issues while offline: isq issue create --title "New issue" queues the operation for later sync.
- Use isq issue list --tree to inspect parent-child relationships and plan triage.
- Automate cleanup after a merged PR with isq cleanup to remove worktree and revert issue state.
FAQ
Yes. Reads come from the local SQLite cache instantly. Write operations are queued locally and synced by the daemon when you reconnect.
How does isq integrate with git?
isq start <id> creates a git worktree and branch for the issue, adds commit hooks to append issue references, and tracks the worktree association for automatic cleanup.