skills.rest
adrielp
adrielpCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

experimental_pr_workflow

Create Linear tickets and pull requests from existing commits.

20|6|Updated Jan 16, 2026
Search Tags:#git#pull-request#ticketing#pr-management#experimental-workflow#workflow-hygiene
One-click install
npx skills add https://github.com/adrielp/ai-engineering-harness --skill experimental-pr-workflow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: experimental_pr_workflow
Source: https://github.com/adrielp/ai-engineering-harness/tree/main/gemini/skills/experimental_pr_workflow
Command: npx skills add https://github.com/adrielp/ai-engineering-harness --skill experimental-pr-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Experimental features often proceed without formal tracking, making it hard to review, document, and integrate later.

Core Features & Use Cases

  • Retroactively create Linear tickets and PRs from existing commits to formalize exploratory work.
  • Extract context from commits and branch history to inform tickets and PR descriptions.
  • Provide guardrails to ensure proper branch naming and PR linkage.

Quick Start

Run the workflow to retroactively create a ticket and PR from recent commits using Gemini CLI.

Frequently Asked Questions about experimental_pr_workflow

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

FAQPage Schema
How do I create Linear tickets from existing git commits?▼

You can retroactively create Linear tickets from existing git commits by running this workflow to extract context from branch history and automatically generate formal tracking tickets.

How do I formalize pull requests for experimental feature branches?▼

To formalize pull requests for experimental feature branches, this workflow extracts commit history and applies guardrails to enforce proper branch naming and PR linkage for your exploratory work.

Do I need GitHub CLI to formalize experimental git workflows?▼

Yes, you need GitHub CLI and git access to formalize experimental git workflows, as the workflow relies on these tools to read branch history and enforce PR linkage.

What is the best way to track exploratory work that lacks formal tickets?▼

Tracking exploratory work that lacks formal tickets is best handled by retroactively extracting context from commits to generate missing tickets and formalize pull requests.

Can I enforce branch naming conventions when creating pull requests from rapid experiments?▼

Yes, you can enforce branch naming conventions when creating pull requests from rapid experiments, as the workflow applies guardrails to ensure proper branch naming and PR linkage.

Related Skills

Explore More Software Engineering Skills→
wyattjohwyattjoh
1

pr-create

Create and update GitHub pull requests from commit history and templates.

Community
Advanced
bradtaylorsfbradtaylorsf
8

ticket-status-sync

Synchronizes Linear ticket statuses with Git workflow events via API and gh CLI.

Community
Advanced
YanCheng-goYanCheng-go
3

commit

Automate branch creation, commits, PR review, and gated merge with human approval.

Community
Advanced
nesihaver-ILnesihaver-IL

create-issue

Create structured issues in GitHub Issues, Linear, or Jira.

Community
Intermediate