refactor: simplify harness setup to one instruction-only skill - #2
Merged
Conversation
pftg
marked this pull request as ready for review
September 9, 2026 18:53
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
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
Follow-up to #1, implementing the request for an AI-instructions-only plugin without Python
or redundant authoring helpers.
harness-setupto 0.2.0./harness-setup:setup.If unavailable, return a creation brief and todo instead of installing or building a duplicate.
todos into one workflow.
Behavior and boundaries
The package contains six files: one skill, one optional reference, manifest, README, changelog
and license. There are no bundled scripts, agents, hooks, MCP servers or replacement validators.
Assessment is read-only by default. Eligible project-owned edits require review of the exact
candidate, explicit approval and a fresh baseline check. Preserve unrelated settings and every
existing permission protection; global/shared configuration, model/provider routes, hooks and MCP
definitions remain owner tasks.
These are AI instructions, not an enforcement layer. No automatic backups, transactional apply,
authenticated approval mechanism or guaranteed rollback is claimed. Reused skills must not run
scripts, installers or code-based evaluations as part of this workflow.
Validation
cases were added; this is not a GitHub maintainer approval.
git diff --checkpass.metadata is unchanged.
frontmatter fields. The unmodified skill is not claimed to pass that narrower portable schema.
Historical 0.1.0 test/CI results do not validate this revision.
Migration and merge gate
This is a breaking simplification: the former updater commands and
/harness-setup:verifyareremoved. Old bundles and consuming-project settings are not automatically changed. Use a clean
updated plugin copy rather than retaining old scripts from a manual installation.
Keep this PR in draft until those gates are satisfied. No merge, plugin installation or live
harness configuration change is requested.