feat(skills): add harness integration to tentacle-creator skill#738
Merged
Conversation
Add ## Harness Integration section to tentacle-creator/SKILL.md so that when this skill generates a tentacle-orchestration skill, it always: - Includes sk harness check in Phase 3 verification gate - Instructs sk harness init when harness.yaml is absent - Wires harness into the generated CONTEXT.md template This completes the harness integration originally requested alongside tentacle-orchestration: both creator and orchestration skills now explicitly name quality-over-speed and harness commands. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Adds explicit harness guidance to the tentacle-creator meta-skill so that newly generated tentacle-orchestration skills consistently preserve/require harness verification steps and bootstrap instructions.
Changes:
- Adds a new Harness Integration section to
.github/skills/tentacle-creator/SKILL.md. - Documents expectations for generated skills: include a Harness gate in Phase 3, instruct
sk harness initwhenharness.yamlis missing, and includesk harness check [--json]in generated CONTEXT templates. - Adds a simple grep-based quality gate to verify the generated orchestration skill includes a Harness gate row.
|
|
||
| ```bash | ||
| if ! grep -qF '.octogent/' .gitignore 2>/dev/null; then | ||
| echo -e "\n# Tentacle orchestration (local work contexts)\n.octogent/" >> .gitignore |
Owner
Author
There was a problem hiding this comment.
Fixed in 62c0fc1 — replaced echo -e with printf for portability on macOS/BSD.
Comment on lines
+188
to
+189
| Present a summary: project profile, files created, agent mappings detected, verification commands, and example usage commands. | ||
|
|
Owner
Author
There was a problem hiding this comment.
Fixed in 62c0fc1 — Step 7 Report now explicitly mentions the harness bootstrap check.
|
|
||
| **Quality over speed.** When this skill generates a `tentacle-orchestration` skill for a project: | ||
|
|
||
| 1. **Always include `sk harness check` in Phase 3 verification** — add a Harness gate row to the generated skill's Phase 3 table so agents never skip harness gates. |
Owner
Author
There was a problem hiding this comment.
Fixed in 62c0fc1 — changed to 'ensure it stays present' to match the canonical reference already having the row.
Comment on lines
+226
to
+229
| # Check harness health before tentacle dispatch | ||
| sk harness check --json | ||
| # If harness.yaml missing, initialize first: | ||
| sk harness init --yes |
Owner
Author
There was a problem hiding this comment.
Fixed in 62c0fc1 — swapped order to bootstrap-first: sk harness init --yes then sk harness check --json.
|
|
||
| > **Quality gate:** A generated skill that omits the harness gate row from Phase 3 is incomplete. Verify with: | ||
| > ```bash | ||
| > grep -q 'harness' .github/skills/tentacle-orchestration/SKILL.md || echo "FAIL: harness gate missing" |
Owner
Author
There was a problem hiding this comment.
Fixed in 62c0fc1 — grep now targets the specific Phase 3 table row string instead of broad 'harness'.
- Use printf instead of echo -e (Step 5, portability on macOS/BSD) - Step 7 Report: mention harness bootstrap check explicitly - Harness §1: 'ensure stays present' not 'add' (already in canonical ref) - Harness code block: init-if-missing → check order (bootstrap first) - Quality gate grep: match specific Phase 3 table row string, not broad 'harness' Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.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
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
Completes the harness integration originally requested for both
/tentacle-orchestrationand/tentacle-creatorskills.PR #737 covered tentacle-orchestration; this PR covers tentacle-creator — the skill that generates tentacle-orchestration skills for new projects.
Change
.github/skills/tentacle-creator/SKILL.md— added## Harness Integrationsection (20 lines):sk harness checkin Phase 3 verification gate rowsk harness initwhenharness.yamlis absentsk harness check [--json]into the generated CONTEXT.md templategrep -q 'harness' .github/skills/tentacle-orchestration/SKILL.mdWhy
The user's original request was: update /tentacle-orchestration and /tentacle-creator skills to always use harness, quality over speed. PR #737 missed tentacle-creator (it was an untracked directory added as a new file in this commit).
Verification
No Python files changed — no test suite required. Markdown only.