From flow
Fetch the current Linear issue's description and plan for context. Use when you need to understand what you're working on, the requirements for the current task, the acceptance criteria, or when the user mentions "the issue", "the ticket", "the task", or asks about the current work context.
npx claudepluginhub artu-ai/flow --plugin flowThis skill is limited to using the following tools:
This skill retrieves the current Linear issue's details to provide context about the work being done.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Performs token-optimized structural code search using tree-sitter AST parsing to discover symbols, outline files, and unfold code without reading full files.
This skill retrieves the current Linear issue's details to provide context about the work being done.
Get the current branch:
git branch --show-current
Linear branch names typically follow the format:
username/abc-123-descriptionabc-123-descriptionExtract the issue identifier (e.g., ABC-123) using a pattern like letters-numbers.
If an issue ID was mentioned in the conversation, use that.
If the branch name doesn't match the Linear ABC-123 pattern and no issue ID was mentioned in conversation, inform the user:
No Linear issue linked to this branch. This branch doesn't appear to be associated with a Linear issue. Issue context is only available for Linear-linked branches.
Do not proceed with fetching.
Use the get_issue tool with the issue ID:
get_issue(id: "ABC-123")
This returns:
After fetching, summarize the relevant parts based on what the user needs:
Issue: ABC-123 - Implement user authentication
Description:
Add JWT-based authentication to the API with the following requirements:
- Login endpoint with email/password
- Token refresh mechanism
- Logout endpoint that invalidates tokens
Acceptance Criteria:
- [ ] Users can log in with valid credentials
- [ ] Tokens expire after 24 hours
- [ ] Refresh tokens work correctly
Status: In Progress
Priority: High