skills.rest
icarloscornejo
icarloscornejoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

load

Imports Jira, Linear, or GitHub Issues tickets into local doer intake.

Updated May 3, 2026
Search Tags:#automation#Linear#Jira#GitHub Issues#import#ticketing#metadata.json
One-click install
npx skills add https://github.com/icarloscornejo/doer --skill load-icarloscornejo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: load
Source: https://github.com/icarloscornejo/doer/tree/main/skills/load
Command: npx skills add https://github.com/icarloscornejo/doer --skill load-icarloscornejo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Importing tickets from Jira, Linear, or GitHub Issues into the local doer intake eliminates manual data entry and accelerates setup for new work items.

Core Features & Use Cases

  • Auto-tracks tickets from common backends and writes a ready-to-use metadata.json.
  • Detects tracker type from IDs or accepts an explicit --tracker to ensure correct routing.
  • Generates a minimal yet complete intake with description, AC extraction, labels, and a branch for development.
  • Supports dry-run and safe, atomic writes to preserve data integrity.

Quick Start

Run /wk:load <ID> to import a ticket into the local doer intake.

Frequently Asked Questions about load

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

FAQPage Schema
How do I import tickets from Jira, Linear, or GitHub Issues into a local workflow intake?▼

To import tickets from Jira, Linear, or GitHub Issues, you can use a tool that auto-detects the tracker from the ticket ID and writes an auditable metadata.json file for downstream processing. This eliminates manual data entry and accelerates setup.

How does auto-detecting a tracker type work when importing a ticket ID?▼

Auto-detecting a tracker type works by parsing the ticket ID format to identify whether it originates from Jira, Linear, or GitHub Issues. Alternatively, you can explicitly specify the tracker using a flag to ensure correct routing and metadata extraction.

What is included in the metadata.json file when importing a ticket?▼

The metadata.json file includes a minimal yet complete intake record containing the ticket description, acceptance criteria extraction, labels, and a designated branch for development. It is written atomically to ensure data integrity and provide an auditable trail for downstream stages.

Can I test ticket import logic without modifying my local intake data?▼

Yes, you can test ticket import logic without modifying local data by using a dry-run mode. This allows you to safely preview the generated intake metadata and verify tracker routing before performing atomic writes to your system.

What is the best way to automate ticket intake from multiple issue trackers for development?▼

The best way to automate ticket intake from multiple issue trackers is to use a command-line import tool that unifies routing for Jira, Linear, and GitHub Issues. It automatically extracts descriptions and acceptance criteria, generating a standardized metadata file for immediate development use.

Why should I use an atomic write process when importing issue tracker data?▼

You should use an atomic write process when importing issue tracker data to preserve data integrity and prevent partial or corrupted metadata.json files. This ensures downstream workflow stages always have a complete, auditable record of the imported ticket.

Related Skills

Explore More Software Engineering Skills→
mvillmowmvillmow
18

gh-get-review-comments

Retrieve GitHub pull request review comments via the GitHub API.

Community
Basic
crbnoscrbnos
2.3k

conductor

Automate work item loops through doer, gate, judge, and ledger phases.

Official
Advanced
brandtambrandtam

new-ticket

Create tickets via guided intake, wiki pages, and optional mirroring.

Community
Advanced
wachawowachawo

to-issues

Decompose project specifications into vertical slices with dependency mapping.

Community
Advanced