Ryan Roga
Community@rogadev · Cumberland, British Columbia, Canada
Full-Stack Web Developer
Agent Skills by Ryan Roga
Showing 3 vetted skills indexed across 1 GitHub repositories.
rogadevnewissue
Converts rough ideas into self-contained GitHub issues filed via the gh CLI.
rogadevupdate-orc
Updates an installed orc pack to the latest GitHub release using cumulative changelog migration maps.
rogadevorc
Orchestrates subagent-driven development to pick, implement, review, and commit GitHub issues autonomously.
Frequently Asked Questions About Ryan Roga
FAQPage SchemaWhat tasks can I accomplish with rogadev's orc-pack skills?▼
Three capabilities: file detailed, self-contained GitHub issues from rough ideas with duplicate and drift checks; orchestrate units of work via implementer and reviewer subagents that loop until clean, then commit; and update an installed orc pack to the latest release from any older version in one pass.
Who is the orc-pack designed for?▼
Full-stack developers running Claude-based coding environments who want unsupervised, subagent-driven execution of board issues. It suits engineers who delegate implementation and review cycles to subagents and need structured issue filing plus managed pack upgrades inside a .claude/ directory.
How do I invoke the orc-pack skills in practice?▼
Trigger skills with slash commands or natural phrases: '/newissue' or 'file an issue' for issue creation, '/orc' or 'pick up the next issue' for orchestration, and '/update-orc' or 'update the orc pack' for upgrades. The orc skill ends with FINISHED, FINISHED (no build), or NOT FINISHED.
What are the prerequisites and dependencies for orc-pack?▼
You need an existing orc pack copied into a .claude/ directory, the GitHub CLI (gh) for issue filing and release fetching, and a repository with a ready check for the orchestrator's commit step. The updater dispatches an orc-updater subagent running Opus 4.8.
Does the newissue skill file issues automatically without approval?▼
No. The skill explicitly requires the user to request or approve an issue before filing. If it surfaces an idea on its own, it presents the suggestion and asks first, then investigates the code, checks the board for duplicates, and files with gh only after confirmation.