task-routing

Route issues to the correct GitHub repo using CLAUDE.md routing config.

215|26|Updated Dec 15, 2025
One-click install
npx skills add https://github.com/serejaris/personal-corp-skills --skill task-routing-serejaris
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-routing
Source: https://github.com/serejaris/personal-corp-skills/tree/main/skills/task-routing
Command: npx skills add https://github.com/serejaris/personal-corp-skills --skill task-routing-serejaris

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

In a multi-repo setup, issues often get created in the wrong repository, causing wasted effort and delays.

Core Features & Use Cases

  • Reads the Task Routing config block from CLAUDE.md in the current project to determine routing rules.
  • Matches user task keywords to the target repository, ensuring correct routing for new issues and backlog items.
  • Performs duplicate checks in the target repo and unified project; avoids creating duplicates.
  • Validates labeling rules and ensures labels are applied or deferred to the weekly-planning flow.

Quick Start

Copy or install the Task Routing skill into your Claude Code skills directory and begin routing requests.

Frequently Asked Questions about task-routing

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

FAQPage Schema
How do I route GitHub issues to the correct repository in a multi-repo setup?

To route GitHub issues across multiple repositories, this Skill reads the Task Routing configuration block from CLAUDE.md and matches task keywords to the appropriate target repo before creating the issue.

How does duplicate checking work when creating issues across multiple repos?

Duplicate checking for issue creation scans the target repository and unified project to verify existing issues, preventing duplicates before routing the new task to the matched repository.

Do I need a specific configuration in CLAUDE.md to use automated task routing?

Yes, automated task routing requires an explicit routing configuration block defined within your project's CLAUDE.md file to determine the keyword matching rules for target repositories.

Can I automatically apply labels to GitHub issues when routing them to different repos?

Labeling is not applied directly during task routing; instead, label validation ensures rules are met and defers label application to the weekly-planning workflow.

What's the best way to prevent issues from being created in the wrong GitHub repository?

The best way to prevent misdirected issue creation is using CLAUDE.md routing rules that match task keywords to target repos while enforcing safe behavior by avoiding unintended repositories.

What happens if task routing cannot find a matching repository for my keywords?

Task routing enforces safe behavior by avoiding unintended repositories; if no explicit keyword match is found in the CLAUDE.md routing block, the issue is not created in a wrong repo.