'linear' 검색 결과

Turn previously fetched pull request reviews into an ordered action plan. Separate distinct findings, track deferred work in Linear, validate that every triage decision is complete, and produce JSON and Markdown files for the implementation phase.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning responses to fetched PR review feedback
• Separating multiple findings within a single review
• Tracking deferred review work in Linear

Prepare feature work by reading a Linear ticket and its context, checking development tools, and looking for existing implementation or pull requests. Route requested PR changes to a separate review workflow before development proceeds.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review a feature ticket before starting development
• Check for existing implementation or an active PR
• Confirm development tools and branch setup

Turn a work-items.md file (produced by /plan-work-items) into Linear issues, one per slice, in a single target Linear team. Use when you want to publish work items as Linear issues, create implementation tickets to track in Linear, or push a broken-down plan into a Linear team. Requires a configured Linear MCP server and a target team. Reads the team's real workflow states, labels, Projects, and members and resolves every option against them before creating anything; defaults each issue to the team's initial state, unassigned, uncategorized, with no parent or Project unless you ask. Links within-file `Depends on` relationships as native Linear "blocked by" relations and annotates the source file so re-runs resume cleanly. Does not produce the work-items file itself — use plan-work-items first. Does not post to Jira — use work-items-to-jira. Does not post to GitHub — use work-items-to-issues.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design a shared notification workflow across GitHub, Linear, local hooks, desktop alerts, and existing communication tools. Classify urgency and ownership, merge duplicate events, and decide which updates need immediate attention, a digest, or a log entry.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Consolidate GitHub, Linear, and local hook notifications
• Reduce duplicate alerts for CI failures
• Separate urgent alerts from digest updates

Configure Factory board behavior and GitHub or Linear event handlers in deployment code. Adjust stage transitions, phase meanings, and tool-result handling, then check the changes with focused tests and versioned audit records.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add approval requirements to board transitions
• Change GitHub or Linear event handling
• Define custom board phases and tool-result rules

Prepare new hires' onboarding from Google Workspace group records and documented role standards. Plan accounts and memberships, invite hires to Slack channels, and create first-week Linear checklists, while holding Workspace access changes for human approval.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare accounts and first-week tasks before a new hire starts
• Choose groups and Slack channels using role and team standards
• Track account creation and memberships awaiting approval

Organize work in Linear with clear issue ownership, priorities, completion criteria, and delivery plans. Helps structure cycles, meaning time-boxed work periods, define project milestones, and plan automated status updates through GitHub integrations or the GraphQL API.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Standardize issue descriptions and completion criteria
• Plan work in two-week cycles
• Set up incoming issue triage

Manages Linear issues, teams, and projects via CLI. Lists issues, creates tasks, views details, links issues, and runs GraphQL queries. Must use for "my Linear issues", "create Linear task", "link issues in Linear", "Linear API query", or any Linear project management request.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

문서·대화·프로젝트 정보를 알맞은 저장 위치로 정리합니다. 로컬 파일, 지식 기반, GitHub 등을 아우르며 중복 확인, 동기화, 검색을 진행합니다.

• 문서와 대화를 지식 기반에 저장
• 중복된 메모 정리
• 여러 저장 위치의 지식 동기화

Investigates GitHub or Linear issues through code, change history, and reproduction attempts. Produces a structured handoff covering causes, assumptions, effort, and impact, then requests the appropriate Factory workflow stage update when applicable.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating the root cause of a reported bug
• Checking for duplicate issues or regressions
• Preparing findings for whoever plans the fix

Investigate opaque errors in shipped OpenWork builds using local logs and Sentry exception reports. Identify the change that caused the failure, reproduce it on the affected runtime, file a Linear issue, and reply to the original report.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating unexplained errors in shipped OpenWork builds
• Identifying the PR that introduced a failure
• Reproducing errors on the affected runtime

Turn a sales call transcript into an updated HubSpot deal, Linear tasks for commitments, and a recap email draft. Ambiguous deal matches are flagged for a person to check, and the email stays unsent for the representative's review.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Update deal records after a sales call
• Create follow-up tasks for promises made on a call
• Draft a recap email for representative review

Find Linear issues by text, assignee, or status, and read their details and comments. Prepare new issues, comments, and status changes for user approval, then return identifiers and links so results can be checked.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find issues by assignee or status
• Read an issue and its comments
• File a bug as a new issue

Draft a Linear project update by comparing current issues with the previous report. Explain progress, added scope, schedule risks, and one needed decision, then publish the update to the project after the user approves it.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing a project status update
• Explaining schedule risks to stakeholders
• Reporting work added since the last update

Find Linear issues reporting the same underlying bug, compare their evidence, and propose which issue to keep. After approval, transfer unique findings and relevant people’s details, then close duplicates with links to the surviving issue.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Clean up duplicate bug reports in a backlog
• Check whether a bug has already been reported
• Consolidate reproduction steps and logs

Turn validated Codex Security findings into tracked work in Linear, Jira, GitHub issues, or draft GitHub security advisories. Check for duplicates, preview exact content and audience, and record approved creations, updates, or reuse.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create issues from validated security findings
• Find and reuse existing issues for the same finding
• Register a reviewed batch of security issues

Fetch a Linear ticket's title + description (the source of all warp route parameters) from a ticket ID or URL, using whichever Linear access the agent has — a Linear integration/tool if present, otherwise the Linear GraphQL API with LINEAR_API_KEY — and halt clearly if no access is configured. Referenced by every warp deploy/update skill that reads a ticket.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Perform actions in Linear (read, create, update, search issues, projects, comments, teams, cycles, labels, etc.) by writing and running small Node scripts against the official @linear/sdk TypeScript SDK with a personal API key. Use this when the user wants to do Linear work from the terminal without the Linear MCP server, or asks to list/open/create/update/close Linear issues, leave comments, or query teams, projects, users, or workflow states.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Perform actions in Linear (read, create, update, search issues, projects, comments, teams, cycles, labels, etc.) by writing and running small Node scripts against the official @linear/sdk TypeScript SDK with a personal API key. Use this when the user wants to do Linear work from the terminal without the Linear MCP server, or asks to list/open/create/update/close Linear issues, leave comments, or query teams, projects, users, or workflow states.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Scan Gmail (default: today's inbox), produce an anonymized summary with action points, then export each email to Linear as an issue with a sensible priority. No personal details — names, email addresses, or company identifiers — ever leave the summary or reach Linear. Use when the user types /gmail-linear-exports, or asks to turn their inbox into Linear issues / export emails to Linear.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Scan Gmail (default: today's inbox), produce an anonymized summary with action points, then export each email to Linear as an issue with a sensible priority. No personal details — names, email addresses, or company identifiers — ever leave the summary or reach Linear. Use when the user types /gmail-linear-exports, or asks to turn their inbox into Linear issues / export emails to Linear.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Coordinate work across apps connected through Aident Loadout, such as finding issues and sharing summaries. The skill checks available actions, account connections, and costs, then obtains required approval before changing external data.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Summarizing assigned Linear issues in Slack
• Checking costs before scraping web pages
• Finding available actions for connected apps

Build HTML/CSS pages styled after a named brand using 54 design references. Templates provide colors, typography, spacing, component styles, responsive behavior, and font substitutes to guide a consistent visual result.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create a landing page with Stripe-inspired styling
• Style a content site after Notion
• Build a dark dashboard inspired by Linear

Draft and refine Linear or Superset tickets using a consistent structure for context, references, and implementation notes. Clarify the desired outcome, record where requests came from, and add code details when enough context is available.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Draft a bug report or feature request
• Standardize ticket structure across a team
• Record feedback sources and links