linear
Use Symphony's `linear_graphql` tool for raw Linear GraphQL operations during app-server sessions.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Use Symphony's `linear_graphql` tool for raw Linear GraphQL operations during app-server sessions.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when any Mister Smith request touches Linear, GitHub PR flow, packet slicing, review state, workspace hygiene, or bootstrap readiness and needs the correct Smith MCP route first.
Use after a Mister Smith SpecKit packet has been created and needs post-spec closure: packet verification, git closure, Linear materialization, honest execution-lane preparation, and follow-on execution readiness without implementation unless explicitly requested.
Use when the user wants a complete Mister Smith live runtime session or workflow evaluation with real execution, durable evidence capture, and honest task/session/autonomy proof instead of mock-only validation.
Use when Mister Smith needs spec-only frontier packet work: turning current repo truth or a pre-SpecKit primer into a new product-side SpecKit packet, or running the full local SpecKit authoring chain for an already chosen packet. Trigger for requests to create or extend a Mister Smith packet spec, pre-SpecKit primer, specify-init prompt, or full spec bundle without implementation.
Use when a Mister Smith SpecKit phase or tasks pack needs to be turned into deterministic Linear slices, blocker chains, prep-slice opportunities, and direct-execution-ready work.
Legacy-named skill for Mister Smith tasks that span Linear control-plane state, GitHub PR flow, local repo truth, lifecycle recovery, or workspace hygiene.
| name | linear |
| description | Use Symphony's `linear_graphql` tool for raw Linear GraphQL operations during app-server sessions. |
Use this skill for direct Linear GraphQL work inside Symphony-managed Codex sessions.
Use the linear_graphql client tool exposed by Symphony. It reuses the session's configured Linear auth.
Tool input:
{
"query": "query or mutation document",
"variables": {
"optional": "graphql variables object"
}
}
Rules:
errors array as failure even if the tool call itself succeeds.query IssueByKey($key: String!) {
issue(id: $key) {
id
identifier
title
description
url
branchName
state {
id
name
type
}
project {
id
name
}
attachments {
nodes {
id
title
url
sourceType
}
}
}
}
query IssueTeamStates($id: String!) {
issue(id: $id) {
id
team {
id
key
name
states {
nodes {
id
name
type
}
}
}
}
}
mutation CreateComment($issueId: String!, $body: String!) {
commentCreate(input: { issueId: $issueId, body: $body }) {
success
comment {
id
url
}
}
}
mutation UpdateComment($id: String!, $body: String!) {
commentUpdate(id: $id, input: { body: $body }) {
success
comment {
id
body
}
}
}
mutation MoveIssueToState($id: String!, $stateId: String!) {
issueUpdate(id: $id, input: { stateId: $stateId }) {
success
issue {
id
identifier
state {
id
name
}
}
}
}
mutation AttachGitHubPR($issueId: String!, $url: String!, $title: String) {
attachmentLinkGitHubPR(
issueId: $issueId
url: $url
title: $title
linkKind: links
) {
success
attachment {
id
title
url
}
}
}
When you do not know an input type or mutation shape, use targeted schema introspection:
query ListMutations {
__type(name: "Mutation") {
fields {
name
}
}
}