github-projects-agile-linkage

Implement Jira-like issue taxonomy, dependencies, and branch/PR linkage in GitHub.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/chf3198/devenv-ops --skill github-projects-agile-linkage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-projects-agile-linkage
Source: https://github.com/chf3198/devenv-ops/tree/main/skills/github-projects-agile-linkage
Command: npx skills add https://github.com/chf3198/devenv-ops --skill github-projects-agile-linkage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Align GitHub issues, sub-issues, dependencies, and branch/PR workflows to support Jira-like planning and linkage.

Core Features & Use Cases

  • Issue taxonomy & labeling: standardize types and labels to enable consistent planning.
  • Hierarchy & dependencies: create sub-issues and explicit blocked-by/blocking links.
  • Dev linkage: associate issues with branches and PRs for traceability.
  • PR close linkage: support closing keywords and automated state updates.
  • Projects fields: enforce status, priority, iteration, and owner across projects.
  • Built-in workflows: auto-add, status sync, and auto-archive to keep work moving.

Quick Start

Configure GitHub Agile Linkage across a repository to enforce issue types, dependencies, and branch/PR linkages.

Frequently Asked Questions about github-projects-agile-linkage

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

FAQPage Schema
How do I enforce agile linkage between GitHub issues and pull requests?

You can enforce agile linkage by standardizing issue taxonomy, creating explicit dependency links, and associating branches and PRs with issues. This ensures traceability and automated state updates across your repository or organization.

Can I track sub-issues and dependencies in GitHub like in Jira?

Yes, you can create sub-issues and explicit blocked-by or blocking dependency links within GitHub. This enables Jira-like planning and hierarchy management directly in your repositories.

How do I set up automated workflows for GitHub project fields and status?

Automated workflows can auto-add issues, sync statuses, and auto-archive items to keep projects moving. You can enforce fields like status, priority, iteration, and owner across your projects.

What is the best way to standardize issue types and labels for agile planning in GitHub?

The best way is to apply consistent issue taxonomy and labeling across teams. This standardization enables reliable planning, dependency tracking, and automated branch and PR linkage.

Does closing a pull request automatically update the linked GitHub issue status?

Yes, PR close linkage supports closing keywords and automated state updates. When you close a pull request, the associated issue reflects the state change automatically.

How do I configure consistent issue taxonomy across multiple GitHub teams?

You can configure issue taxonomy at the repository or organization level to enforce consistent types and labels. This ensures all teams follow the same planning and linkage controls.