manager

Syncs session data with GitHub issues and queries status across repositories.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Bridges your current AI-assisted session with GitHub Issues to keep tasks visible, traceable, and aligned with project governance. It prevents end-of-session slips by ensuring updates are captured, issues are properly linked to epics, W-labels, and Project boards, and it avoids creating or misplacing orphan tasks.

Core Features & Use Cases

  • Write mode (sync): at session end, finds matching issues, updates bodies, appends a work-record comment, attaches to a parent epic, enforces W-labels and project placement, and creates new issues only when nothing matches.
  • Read mode (query): anytime: cross-repo search for tracks, shows a compact plan of open issues with their parent epics and projects, and surfaces health checks and drift signals.
  • Iron invariants and setups: relies on CLAUDE.md Manager Config for project boards, W-label conventions, and non-empty parent relationships to keep the workflow safe and auditable.
  • Triggers: responds to commands like /manager, sync session, or status queries across repos.

Quick Start

Invoke the skill by saying "sync session" or "/manager" to start a write-mode plan and execution, or ask for a status lookup to start a read-mode query.

Frequently Asked Questions about manager

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

FAQPage Schema
How do I sync AI session work with GitHub issues?▼

To sync AI session work with GitHub issues, invoke a write mode command like "sync session" to find matching issues, update their bodies, append work-record comments, and enforce parent epic links alongside W-labels before finalizing.

What is the best way to track project management tasks across multiple GitHub repositories?▼

Tracking project management tasks across multiple GitHub repositories is achieved through read mode queries that cross-search open issues, display a compact plan, and surface health metrics to keep work current and aligned with epics.

How do I prevent orphaned tasks when creating GitHub issues from session work?▼

To prevent orphaned tasks when creating GitHub issues, the workflow enforces iron invariants and non-empty parent relationships, ensuring new issues are only created when no existing match exists and always attaching them to a parent epic.

Do I need a specific configuration to link GitHub issues to epics and project boards?▼

You need a configurable Manager config in CLAUDE.md to link GitHub issues to epics and project boards, which establishes project board placements, W-label conventions, and parent relationships to keep the workflow auditable.

Can I check GitHub issue health and drift signals across repositories?▼

You can check GitHub issue health and drift signals across repositories by triggering a read mode status lookup, which surfaces health checks and compact plans of open issues alongside their parent epics and projects.