skills.rest
simon-downes
simon-downesCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

tool-issues

Create, update, list, comment, and transition issues across GitHub and Linear.

2|Updated Mar 27, 2026
Search Tags:#automation#workflow#github#linear#issues#tracking#provider-dispatch
One-click install
npx skills add https://github.com/simon-downes/archie --skill tool-issues
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tool-issues
Source: https://github.com/simon-downes/archie/tree/main/persona/skills/tool-issues
Command: npx skills add https://github.com/simon-downes/archie --skill tool-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Managing issues across multiple providers is fragmented and manual; this skill unifies operations across providers like GitHub Issues and Linear, enabling consistent workflows.

Core Features & Use Cases

  • Unified operations: list, get, create, update, comment, and status transitions across providers.
  • Provider-aware mapping: automatically translates generic fields to provider-specific semantics via project config.
  • Plan storage and collaboration: attach or extract plan content within issues for traceability.

Quick Start

Ask me to create an issue in the current project using the configured provider.

Frequently Asked Questions about tool-issues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track issues across both GitHub and Linear in a unified workflow?▼

You can unify issue tracking across GitHub and Linear by using a single interface that maps generic operations to provider-specific semantics loaded from project config references.

Can I create and transition issues in Linear using generic commands?▼

Yes, creating and transitioning Linear issues is supported through a unified interface that translates generic commands into Linear-specific fields using provider references and project configuration.

What is needed to configure cross-provider issue tracking for a project?▼

Cross-provider issue tracking requires a project config specifying the issues.provider field, along with provider references that map unified operations to provider-unique fields.

Does this issue tracking approach support listing and commenting on GitHub Issues?▼

Yes, listing and commenting on GitHub Issues are supported operations within the unified interface, alongside creating, updating, and transitioning issues across configured projects.

What is the best way to attach plan content to issues for traceability?▼

Attaching or extracting plan content within issues provides traceability, allowing plan storage and collaboration directly through the unified issue tracking operations across GitHub and Linear.

Related Skills

Explore More Software Engineering Skills→
elijahmurrayelijahmurray
2

setup-ticket-system

Configure GitHub Issues, Linear, Jira, or GitLab for issue tracking.

Community
Basic
endorphin-aiendorphin-ai
3

jira

Manage Jira issues via Atlassian MCP with creation, updates, linking, commenting, and JQL searches.

Official
Advanced
shuff57shuff57

linear

Manage Linear issues, teams, and projects via the GraphQL API.

Community
Intermediate
shllgshllg

forge-adapter

Unify GitHub and Forgejo issue management through a single adapter interface.

Community
Intermediate