work

Process GitHub issues from simplest to hardest with automated PR creation.

4|Updated Sep 24, 2025
One-click install
npx skills add https://github.com/alexmond/yj-schema-validator --skill work-alexmond
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work
Source: https://github.com/alexmond/yj-schema-validator/tree/main/.claude/skills/work
Command: npx skills add https://github.com/alexmond/yj-schema-validator --skill work-alexmond

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Process open GitHub issues from simplest to hardest in a continuous loop, enabling teams to automate triage, prioritization, and incremental delivery without manual toggling.

Core Features & Use Cases

  • Continuous issue triage: gather open issues, rank by estimated complexity, and move through the backlog in order.
  • End-to-end workflow: create feature branches, apply formatting and validations, run tests, and push/merge PRs in a repeatable sequence.
  • Plan-mode for non-trivial work: when issues require design decisions, the workflow can halt for planning and stakeholder review before implementation.

Quick Start

Start processing open GitHub issues from simplest to hardest in a continuous loop.

Frequently Asked Questions about work

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

FAQPage Schema
How do I automate GitHub issue triage and implement fixes end-to-end?

You can automate GitHub issue triage by continuously processing open issues from simplest to hardest, creating feature branches, running tests via mvnw, and triggering PR creation and merge through gh.

How does continuous issue prioritization work for a GitHub backlog?

Continuous issue prioritization works by gathering open GitHub issues and ranking them by estimated complexity, allowing the workflow to move through the backlog incrementally from trivial fixes to architecture changes.

Can I use plan mode for non-trivial GitHub issues that require architecture changes?

Yes, you can use plan mode for non-trivial GitHub issues. The workflow halts for planning and stakeholder review before implementation when issues require design decisions or architecture changes.

Do I need gh and mvnw to automate pull request creation and merging?

Yes, you need gh and mvnw to automate pull request creation and merging. The workflow relies on these tools to trigger PR creation, apply validations, and execute merges in a repeatable sequence.

What is the best way to handle software maintenance workflows on GitHub without manual toggling?

The best way to handle software maintenance workflows on GitHub without manual toggling is using a continuous loop that automates triage, prioritization, and incremental delivery from open issues to merged PRs.

When should I not use continuous automated triage for GitHub issues?

You should not use continuous automated triage for GitHub issues when tasks require complex stakeholder review or nuanced design decisions that cannot be paused effectively using the plan mode halt mechanism.