GitHub Issue & Task Architect FAQs

Question 1

How does the skill handle GitHub labels?

Accepted Answer

It automatically checks for and creates priority labels (high, medium, low) with specific hex codes and descriptions to ensure consistent categorization across the repository.

Question 2

What issue types are supported?

Accepted Answer

The skill supports three distinct types: Epic issues for multi-PR initiatives, PR-scoped issues with auto-closing keywords, and Review issues for non-blocking feedback.

Question 3

Can it distinguish between main and feature branches?

Accepted Answer

Yes, it uses a branch-based decision tree: it creates issues directly on main/develop but prompts for merge necessity when working on a PR branch to avoid redundant issues.

Question 4

Does it support auto-closing PRs?

Accepted Answer

Yes, for PR-scoped issues, it automatically includes keywords like 'fixes', 'closes', or 'resolves' to streamline the repository maintenance workflow.

Question 5

Does it follow Conventional Commit standards?

Accepted Answer

Absolutely. It enforces specific formatting for titles and bodies, including imperative mood, character limits, and proper scope definitions matching your git history.

GitHub Issue & Task Architect

Key Features

Use Cases

GitHub Issue & Task Architect

Key Features

Use Cases