composio-community/awesome-codex-skills

issue-triage

Triage Linear or Jira backlogs and run bug sweeps via the Composio CLI. Bulk-fetch issues, dedupe, relabel, reassign, and post summaries — all from the shell without clicking through the UI.

First seen Apr 25, 2026

Installation

$ npx skills add composio-community/awesome-codex-skills --skill issue-triage

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from composio-community/awesome-codex-skills · top by installs.

npx skills add composio-community/awesome-codex-skills

Browse all from composio-community/awesome-codex-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 16.3K
Default branch master
Open issues 13
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

More metadata
short-description
Linear/Jira triage + bug sweeps via the Composio CLI

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 4,604 B
  • docs SUMMARY.md 209 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 421 installs

SKILL.md

Issue Triage (Linear / Jira)

Drive triage sessions and bug sweeps across Linear or Jira with the Composio CLI. Pull the backlog, cluster duplicates, apply labels, and hand a clean list back to the team.

When to Use

  • Weekly triage: "what's unassigned, stale, or missing a priority?"
  • Bug sweep after a release: "cluster all P1/P2 bugs, dedupe, assign owners."
  • Cross-tool sync: Sentry → Linear, PagerDuty → Jira.

Prereqs

curl -fsSL https://composio.dev/install | bash
composio login
composio link linear        # or: composio link jira

Discover Tools

composio search "list issues" --toolkits linear
composio search "search issues" --toolkits jira
composio tools list linear
composio tools list jira

Common slugs (verify with --get-schema):

Linear

  • LINEARLISTISSUES
  • LINEARCREATEISSUE
  • LINEARUPDATEISSUE
  • LINEARCREATECOMMENT

Jira

  • JIRASEARCHFORISSUESUSING_JQL
  • JIRACREATEISSUE
  • JIRAEDITISSUE
  • JIRAADDCOMMENT
  • JIRAASSIGNISSUE

Triage Workflow

  1. Pull the backlog slice:

```bash # Linear composio execute LINEARLISTISSUES -d '{ "filter": { "state": { "type": { "eq": "unstarted" } }, "assignee": { "null": true } }, "first": 100 }'

# Jira composio execute JIRASEARCHFORISSUESUSING_JQL -d '{ "jql": "project = APP AND statusCategory != Done AND assignee is EMPTY ORDER BY updated DESC", "maxResults": 100, "fields": ["summary","priority","labels","updated","reporter"] }' ```

  1. Cluster by title similarity and labels. The agent groups likely duplicates locally.
  2. Apply updates in one pass (label, priority, assignee):

```bash composio execute LINEARUPDATEISSUE -d '{ "id":"abc-123","priority":2,"labelIds":["label-bug","label-p1"],"assigneeId":"user-42" }'

composio execute JIRAEDITISSUE -d '{ "issueIdOrKey":"APP-482", "fields":{"priority":{"name":"High"},"labels":["bug","p1"]} }' ```

  1. Link duplicates with comments referencing the canonical issue.
  2. Post a digest of what changed to Slack so the team sees the sweep results.

Bug Sweep (Post-Release)

# Jira: every bug filed in the last 7 days, sorted by severity
composio execute JIRA_SEARCH_FOR_ISSUES_USING_JQL -d '{
  "jql":"type = Bug AND created >= -7d ORDER BY priority DESC, created ASC",
  "fields":["summary","priority","labels","reporter","components"]
}' | jq -r '.issues[] | "\(.fields.priority.name)\t\(.key)\t\(.fields.summary)"'

Workflow File

scripts/triage-linear.ts, run with composio run --file scripts/triage-linear.ts:

const { nodes: issues } = await execute("LINEAR_LIST_ISSUES", {
  filter: { state: { type: { eq: "unstarted" } }, assignee: { null: true } },
  first: 100
});

const stale = issues.filter(i => {
  const age = (Date.now() - new Date(i.updatedAt).getTime()) / 86400000;
  return age > 14;
});

for (const i of stale) {
  await execute("LINEAR_CREATE_COMMENT", {
    issueId: i.id,
    body: "Auto-triage: stale for 14+ days. Please assign or close."
  });
}

await execute("SLACK_SEND_MESSAGE", {
  channel: "triage",
  text: `Weekly triage: pinged ${stale.length} stale issues.`
});

Cross-Tool: Sentry → Linear

composio run '
  const hot = await execute("SENTRY_LIST_A_PROJECTS_ISSUES", {
    organization_slug:"acme", project_slug:"api",
    query:"is:unresolved", sort:"freq", limit:5
  });
  for (const s of hot) {
    await execute("LINEAR_CREATE_ISSUE", {
      teamId: "TEAM_ID",
      title: `[Sentry] ${s.title}`,
      description: `${s.permalink}\nCount: ${s.count}`,
      labelIds: ["label-bug","label-from-sentry"]
    });
  }
'

Troubleshooting

  • Unknown field namescomposio execute <SLUG> --get-schema shows the exact filter shape (Linear uses nested objects; Jira uses JQL strings).
  • 403 on Linear → re-run composio link linear with the right workspace.
  • Jira custom fields missing → request them explicitly in the fields array.
  • Bulk edits rate-limited → insert a 250ms sleep in the composio run loop; don't use --parallel.

Full CLI reference: docs.composio.dev/docs/cli