ticket-intake

Parse Notion and GitHub URLs and register tickets in the Pipeline API.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/christian-byrne/ticket-to-pr-pipeline --skill ticket-intake
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ticket-intake
Source: https://github.com/christian-byrne/ticket-to-pr-pipeline/tree/main/skills/ticket-intake
Command: npx skills add https://github.com/christian-byrne/ticket-to-pr-pipeline --skill ticket-intake

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of ingesting new tickets from various sources like Notion and GitHub, ensuring they are registered and ready for the pipeline.

Core Features & Use Cases

  • Source Agnostic Intake: Parses URLs from Notion and GitHub to extract ticket details.
  • API Integration: Registers new tickets in the central Pipeline API and updates their status.
  • Use Case: When a new feature request is logged in Notion, this Skill automatically creates a corresponding ticket in the pipeline, assigns it to the research phase, and updates the Notion status to "In Progress".

Quick Start

Use the ticket-intake skill to process the Notion ticket at https://notion.so/your-ticket-url.

Frequently Asked Questions about ticket-intake

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

FAQPage Schema
How do I automate ticket intake from Notion and GitHub into a development pipeline?

Automating ticket intake from Notion and GitHub involves parsing source URLs to extract ticket details and registering them via API calls. This skill automates that extraction, creates the pipeline ticket, and transitions the source status to 'In Progress'.

What is the process for registering Notion tickets in a central Pipeline API?

Registering Notion tickets in a Pipeline API requires parsing the Notion URL for relevant data and making mandatory API calls for ticket creation. This skill handles the source-specific parsing and verifies successful intake within the pipeline.

Can I use workflow automation to update ticket states across GitHub and Notion?

Yes, workflow automation can update ticket states across GitHub and Notion. This skill ingests ticket information from both platforms, registers the ticket in the Pipeline API, and handles the necessary state transitions to keep sources synchronized.

How do I verify successful ticket registration after extracting data from GitHub URLs?

Verifying successful ticket registration after extracting data from GitHub URLs requires checking the API response post-creation. This skill manages the API integration, performs the mandatory state transition, and handles the verification of successful intake automatically.

Does this ticket intake automation require manual API configuration for parsing URLs?

No manual API configuration is needed for parsing URLs. The skill handles source-specific parsing for Notion and GitHub internally, executing the mandatory API calls required for ticket creation and state transition without external setup.