feat(pipeline): migrate to skills/ structure + add standalone skills#1088
Merged
Conversation
Mirrors the Maestro v0.6.0 restructure for this transplanted workflow. Each commands/<name>.md becomes skills/<name>/SKILL.md; bundled assets (scripts/, refs/) follow their parent skill. - orchestrator/workflows/ → orchestrator/runners/ (avoids collision with the platform's reserved workflows/*.js concept) - init-pr-draft.sh template path updated to .claude/skills/ - All path references updated across 5 agent files, both JS runners, and all SKILL.md files — zero .claude/commands/ references remain Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Thin entry point for grooming-agent. Reads REPO and TEMP_ROOT from the orchestrator's ## Project Config block (no maestro.json). Syncs the issue, invokes grooming-agent in STANDALONE MODE, shows the comment draft, and prompts before posting to GitHub. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Thin entry point for the challenger agent. Reads config from the orchestrator's ## Project Config block. Errors clearly if no spec exists (with pointer to /groom). Prompts before posting to the issue. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Thin entry point for the lead-reviewer agent. Reads config from the orchestrator's ## Project Config block. Resolves PR from argument or current branch, locates spec if it exists, invokes lead-reviewer in STANDALONE MODE, prompts before posting inline comments + summary. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Thin entry point for the qa-engineer agent. Reads REPO, TEMP_ROOT, BOOT_CMD, and LOCAL_URL from the orchestrator's ## Project Config block. Resolves PR from argument or current branch, passes env config to the agent, prompts before posting the QA report. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 4 |
| Duplication | 0 |
🟢 Coverage ∅ diff coverage
Metric Results Coverage variation Report missing for 3b6205a1 Diff coverage ✅ ∅ diff coverage (50.00%) Coverage variation details
Coverable lines Covered lines Coverage Common ancestor commit (3b6205a) Report Missing Report Missing Report Missing Head commit (6797512) 13940 48 0.34% Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch:
<coverage of head commit> - <coverage of common ancestor commit>Diff coverage details
Coverable lines Covered lines Diff coverage Pull request (#1088) 0 0 ∅ (not applicable) Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified:
<covered lines added or modified>/<coverable lines added or modified> * 100%1 Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct.
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Mirrors the Maestro v0.6.0/v0.6.1 restructure for this transplanted workflow.
commands/→skills/layout throughout.claude/Commits
Restructure (1 commit)
.claude/commands/<name>.md→.claude/skills/<name>/SKILL.mdorchestrator/workflows/→orchestrator/runners/(avoids collision with platform'sworkflows/concept)init-pr-draft.shtemplate path updatedcommands/path refs updated in 5 agent files + both JS runnersStandalone skills (4 commits)
/groom <issue>grooming-agent/challenge <issue>challenger/review [PR]lead-reviewer/qa [PR]qa-engineerKey difference from Maestro: these skills read
REPO,TEMP_ROOT,BOOT_CMD, andLOCAL_URLfrom the## Project Configblock in.claude/skills/orchestrator/SKILL.md— nomaestro.jsonneeded.All four pipeline agents (
grooming-agent,challenger,lead-reviewer,qa-engineer) are unchanged.Test plan
/groom <issue>— spec written to.ai/issues/<N>/spec.md, comment draft shown, posting prompt appears/reviewon current branch — review report shown without auto-posting/qa <PR>— env boots, acceptance criteria tested, QA report shown before posting/issue-workflow) — verify restructure didn't break normal operation/challenge <issue>after a groom — APPROVED/NEEDS_REVISION verdict shown🤖 Generated with Claude Code