symphony-go: Skill for Claude Code

Linear GraphQL

Use the linear_graphql tool exposed by Symphony's app-server session for raw Linear API access.

Tool Input

{
  "query": "query or mutation document",
  "variables": { "optional": "graphql variables" }
}

One operation per call. Top-level errors array means the operation failed.

Common Operations

Query an issue

query IssueByKey($key: String!) {
  issue(id: $key) {
    id identifier title
    state { id name }
    project { id name }
    url description
  }
}

Get team workflow states

query IssueTeamStates($id: String!) {
  issue(id: $id) {
    team {
      states { nodes { id name type } }
    }
  }
}

Move issue to a state

mutation MoveIssue($id: String!, $stateId: String!) {
  issueUpdate(id: $id, input: { stateId: $stateId }) {
    success
    issue { id identifier state { name } }
  }
}

Create a comment

mutation CreateComment($issueId: String!, $body: String!) {
  commentCreate(input: { issueId: $issueId, body: $body }) {
    success
    comment { id url }
  }
}

Update a comment

mutation UpdateComment($id: String!, $body: String!) {
  commentUpdate(id: $id, input: { body: $body }) {
    success
    comment { id body }
  }
}

Attach a GitHub PR

mutation AttachPR($issueId: String!, $url: String!, $title: String) {
  attachmentLinkGitHubPR(issueId: $issueId, url: $url, title: $title, linkKind: links) {
    success
    attachment { id url }
  }
}

Schema introspection

query ListMutations {
  __type(name: "Mutation") { fields { name } }
}

query InspectInput($name: String!) {
  __type(name: $name) {
    inputFields { name type { kind name ofType { kind name } } }
  }
}

Post-PR Workflow

After pushing a PR, move the issue to In Review so the orchestrator stops re-dispatching:

1. Fetch the team's workflow states to get the exact stateId for "In Review".
2. Update the issue state:

   mutation MoveIssue($id: String!, $stateId: String!) {
     issueUpdate(id: $id, input: { stateId: $stateId }) {
       success
       issue { id identifier state { name } }
     }
   }
   

3. Attach the PR URL to the issue.