What problem does it solve?
When working across a pseudomonorepo tree with multiple submoduled child repos, GitHub Project tasks that reference context-v files often have broken links or inconsistent formatting, making it hard for collaborators to find the relevant work context and wasting time on manual path translation.
Core Features & Use Cases
- Standardized Task Body Format: Enforces that all task bodies referencing context-v files use clickable GitHub URLs pointing directly to the file in its own repo, eliminating 404 errors from incorrect parent monorepo paths.
- gh CLI Workflow Recipes: Provides ready-to-use command patterns for creating single tasks, bulk-creating tasks from spec sections, adding existing issues to projects, and updating task status fields.
- Pseudomonorepo Integration: Composes with the pseudomonorepos skill to automatically resolve which submoduled repo owns a local context-v file and which branch tier (development/main/master) the link should target.
- Use Case: When creating tasks for work tracked in context-v specs, explorations, or plans across the Lossless pseudomonorepo tree, this skill ensures all task links are valid and consistent for all collaborators.
Quick Start
Use this skill to create a new GitHub Project task that links directly to the relevant context-v file for your current work, with the correct repo and branch automatically resolved.
