skills.rest
agorokh
agorokhCOMMUNITY
Explore all skills by this author →
GitHub

orchestrate

Orchestrate GitHub issues into CI-ready draft pull requests.

Updated Jul 5, 2026
Search Tags:#github#branching#agentic workflow#ci#dependency review#issue to pr#vault memory
One-click install
npx skills add https://github.com/agorokh/applied-ai-research --skill orchestrate-agorokh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orchestrate
Source: https://github.com/agorokh/applied-ai-research/tree/main/.cursor/skills/orchestrate
Command: npx skills add https://github.com/agorokh/applied-ai-research --skill orchestrate-agorokh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It streamlines implementing GitHub issues into compliant, CI-ready draft pull requests without losing architectural context or violating repository invariants.

Core Features & Use Cases

  • Tier-3 substrate preloading: Queries the knowledge graph for prior decisions and invariants related to the issue before any branching or code-path edits.
  • Issue-to-PR delivery routing: Selects the correct primary workflow (feature build, PR resolution, dependency review, release notes, post-merge stewardship) based on issue type and repository conventions.
  • PR hygiene and handoff: Creates a compliant branch, opens a Draft PR early, runs fast CI, marks the PR ready, waits for async bots, and hands off to the PR-resolution subagent.

Quick Start

Provide a GitHub issue number for this repository and ask the orchestrate skill to implement it through a draft PR and resolution-ready handoff.

Frequently Asked Questions about orchestrate

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

FAQPage Schema
How do I automate creating a draft PR from a GitHub issue?▼

You can automate issue-to-PR workflows by loading repository invariants and semantic context before branching, opening an early draft PR, running fast CI validation, and handing off to a resolution subagent for bot thread closure.

What is issue-driven development and how does semantic context loading work?▼

Issue-driven development implements GitHub issues into CI-ready pull requests. Semantic context loading works by querying a Tier-3 knowledge graph substrate for prior architectural decisions and repository invariants before any code-path edits are made.

How do I ensure CI validation passes before marking a pull request ready?▼

CI validation gating works by opening a draft PR early, running fast CI checks, waiting for async bots to close their threads, and only marking the PR ready for review upon successful CI completion and bot thread closure.

Does this agentic workflow support dependency review and post-merge learning workflows?▼

Yes, the agentic workflow supports dependency review and post-merge learning. It routes issue types to primary workflows including feature builds, dependency or tooling bumps, and post-merge stewardship classification across enterprise deployment constraints.

What are the limitations of automating branch hygiene per agent protocol?▼

Limitations include the mandatory requirement for Tier-3 substrate querying and vault or session discipline before edits. Completion is strictly gated on CI and bot thread closure, requiring enterprise deployment constraints to be met for successful PR handoff.

Related Skills

Explore More Software Engineering Skills→
agorokhagorokh

learner

Extract post-merge learnings from pull requests into knowledge graph updates.

Community
Advanced
timothyfroehlichtimothyfroehlich

jules-pr-manager

Aggregate and analyze open Jules PRs to recommend merge or close decisions.

Community
Intermediate
lucidlabs-hqlucidlabs-hq
2

pr

Automate pull request workflows from branch creation to PR closure.

Official
Advanced
agorokhagorokh

post-merge

Sync local main, classify merged PRs, and update vault handoff documents.

Community
Advanced