Workspace skills: apply-report-changes moves in-repo, new github-changes companion#347
Open
bgmcmullen wants to merge 2 commits into
Open
Workspace skills: apply-report-changes moves in-repo, new github-changes companion#347bgmcmullen wants to merge 2 commits into
bgmcmullen wants to merge 2 commits into
Conversation
…ges companion hypaware-apply-report-github-changes files a report's repo-destined proposed changes (ready issue text, ready diffs, cross-repo moves) as GitHub issues and PRs via gh, with per-change approval and no merging. Its machine-local companion hypaware-apply-report-changes moves from a home directory into the workspace so both ride attach to every enrolled machine. Registered in the claude and codex plugin manifests and skill lists. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Resolve skill-list conflicts: keep master's trimmed report-skill roster (superseded adoption/improvement/security/spend skills removed, publish-report added) and append this branch's new hypaware-apply-report-github-changes in both the claude and codex plugin manifests and registration lists. For the add/add codex apply-report-changes SKILL.md, take master's codex-adapted approval wording (no AskUserQuestion). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
What
Two additions to the plugin-shipped skill set (claude + codex copies, registered in both manifests and skill lists):
hypaware-apply-report-github-changes(new). The usage report's proposed changes split into machine-local artifacts and repo-destined ones (ready-to-file issue text, ready diffs for other repos, cross-repo moves). The existing apply skill explicitly classifies the latter as "not applicable here" and stops. This companion covers them: it reads the newest report, presents a numbered list showing the full issue text or branch/diff per change, and files only the user-approved ones as GitHub issues or PRs viagh. It searches for existing issues/PRs first so reruns don't duplicate, files a tracking issue instead of a PR when a change's source lives on another machine, and never merges or pushes to a default branch.hypaware-apply-report-changesmoves into the workspace. It previously existed only in a home directory, which is the exact "home-dir skills silo, in-repo skills spread" pattern the 2026-07-16 usage report calls out. Both apply skills now ride attach to every enrolled machine (LLP 0107).Why now
The 07-16 report's highest-leverage proposed changes are all repo-destined (a server dedup issue, template diffs, a skills-move PR), so none of them could be actioned by the existing machine-local skill.
Testing
npm run smoke -- core_boot_nooppasses (exercises plugin manifest loading and skill registration).npm testhas 8 pre-existing failures on master (scanColumn/graph-projection tests failing insidenode_modules/squirreling0.14.0, "chunks is not async iterable"); verified identical with this change stashed, installed version matches the lockfile. Not addressed here.🤖 Generated with Claude Code