feat(core): add adopting-core-setup-repo reconciliation skill - #12
Merged
Conversation
Operator playbook for piloting core:setup-repo in an EXISTING (partially standardized) repo, extracted from the retina-tracker pilot (#5). Captures the files the engine skips, the ci-python.yml packaged-repo import gotcha, the allowedTools/track_progress requirement for posting review comments, the .gitignore-swallows-.claude issue, public-repo @claude hardening, and the permission_denials_count verification refinement. Bumps core 0.2.0 -> 0.3.0 (new skill). Co-Authored-By: Claude Opus 4.8 (1M context) <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.
Adds a
coreplugin skill capturing the operator playbook for adoptingcore:setup-repoin an existing (partially standardized) repo, extracted fromthe retina-tracker pilot (#5). This is the 6th deliverable of that pilot — the
knowledge was worth preserving where the next operator will find it.
Why in
core(not the pilot repo or a user dir)The value is for the next repo standardization (
retina-gui, Phase 2 stacks),so it belongs next to
setup-repoand ships via the marketplace — not stranded inthe one repo where the pilot is already done.
What it covers
ci-python.ymlinstalls deps but not a packaged repo →ModuleNotFoundErrorinCI →
pythonpath = ["."].track_progress+--allowedTools(inline-comment MCP tool)..gitignorethat ignores.claude/silently drops scaffolded config.@claudehardening viaauthor_associationguard.permission_denials_count > 0can be benign; verify via token scope + a realcomment on a separate non-workflow PR.
Lifecycle note
Several sections describe template gaps tracked in #7–#11. As those land, the
corresponding sections here should be pruned — keeping the skill and the template
in the same repo makes that easy. The durable core is the reconciliation playbook
and the verification refinements.
Bumps
core0.2.0 → 0.3.0.Refs #5.