se-workflow

Automate end-to-end issue-to-PR workflows for GitHub projects.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/ankitpyc/se-workflow --skill se-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: se-workflow
Source: https://github.com/ankitpyc/se-workflow/tree/main
Command: npx skills add https://github.com/ankitpyc/se-workflow --skill se-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end workflow that takes a GitHub repository from orientation to a merged PR, reducing manual coordination and improving consistency.

Core Features & Use Cases

  • Orient on a target repo by reading critical docs (README, PLAN.md) and the source layout to establish context.
  • Pick and assign open issues by priority, then branch and implement following project conventions.
  • Create a feature branch, apply conventional commits, and generate a PR with a structured template.
  • Produce a final self-review and a summary report with next steps for remaining issues.
  • Use case: a sub-agent works across multiple repositories, autonomously handling issue selection, implementation guidance, and PR creation without hand-holding.

Quick Start

Say '/se-workflow <repo>' to begin the end-to-end issue-to-PR workflow on that repository.

Frequently Asked Questions about se-workflow

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

FAQPage Schema
How do I automate the GitHub issue-to-PR workflow end to end?

Automating the GitHub issue-to-PR workflow involves orienting on a repository, selecting high-priority issues, creating a feature branch, guiding implementation, enforcing conventional commits, and generating a structured pull request template.

How does conventional commit enforcement work during automated branch implementation?

Conventional commit enforcement during automated branch implementation applies standardized commit message formatting directly within the feature branch workflow, ensuring consistent repository history and structured pull request generation.

Can I use this automated issue triage across multiple GitHub repositories?

Yes, automated issue triage supports multi-repo GitHub contexts, allowing a sub-agent to autonomously select and assign open issues by priority across different hosted repositories without manual hand-holding.

What do I need to start automating pull request creation for GitHub projects?

To start automating pull request creation, you need a target GitHub repository with accessible documentation like README and PLAN.md, which the workflow reads to establish project context and source layout conventions.

What is the best way to generate a structured PR template after implementing a feature branch?

Generating a structured PR template is best handled by applying conventional commits to the feature branch and then producing a final self-review and summary report with next steps for remaining open issues.

When should I not use an autonomous issue-to-PR workflow for GitHub?

You should avoid autonomous issue-to-PR workflows when a GitHub repository requires complex manual implementation decisions, lacks foundational documentation like a README, or needs custom branching strategies outside conventional commit standards.