feat(skills): add setup-chiptus-env by chiptus · Pull Request #6 · chiptus/skills

chiptus · 2026-09-16T11:34:01Z

Adds setup-chiptus-env, a repo-onboarding skill that installs setup-matt-pocock-skills if missing, runs it for the issue tracker/triage labels/domain docs, optionally relocates docs/agents/ to a separate repo via AGENTS_DOCS_REPO, then scaffolds the autonomic issue pipeline (autonomic-issues.md) wired to whichever tracker (GitHub or Linear) was chosen. Tracker-specific mechanics live in references/github.md / references/linear.md, one file per tracker.

Ported from chiptus/UpLine#499 (now closed) so it installs across repos (via npx skills or the Claude Code plugin) instead of living inside one consuming repo. Design decisions — the reference-file split, the single AGENTS_DOCS_REPO pointer mechanism, the verified npx skills install command — came out of a grilling session recorded in chiptus/UpLine's HANDOFF-setup-chiptus-env.md and tracked as MYP-284.

Note on validation so far: the docs were checked against chiptus/UpLine#499/MYP-284 as a real case, which caught a real gap (the issue↔PR link convention wasn't actually being followed) — but that was a manual walkthrough, not an actual run of the documented pipeline (no Routine has fired, no issue has gone through claim → implement → PR autonomously). The verification steps below are what's still needed before this can be called validated rather than just internally consistent.

Verification

npx skills add chiptus/skills (or the plugin marketplace flow) lists setup-chiptus-env as installable, and installing it onto a throwaway repo does not error.
Run /setup-chiptus-env on a second, different repo (not UpLine) end to end: confirm it installs setup-matt-pocock-skills with the documented flags, correctly reads back the tracker choice, and step 5 points at the right references/*.md file for that tracker without asking twice.
On a repo using GitHub as tracker: complete the "Setup checklist" in autonomic-issues.md for real (create the pipeline labels, create the triage + fix Routines), then let one triage sweep and one fix-firing actually fire — confirm an issue goes needs-triage → ready-for-agent → claimed (agent label) → a real PR opened by the Routine with Closes #<n> in the body, matching references/github.md.
On a repo using Linear as tracker: same, but confirm the PR carries the Linear identifier in its title/body per references/linear.md, and the issue's native status moves In Progress → In Review in step with the PR.
Set AGENTS_DOCS_REPO on a repo that opts into external docs (Portainer is the real candidate) and confirm both a local session and one live Routine firing actually read docs/agents/* from the external repo instead of in-repo — this closes the gap flagged as unverified in the original handoff (whether a cloud Routine can clone a second repo mid-firing).
Add a third tracker's references/<tracker>.md (or confirm none is needed yet) only after one of the above surfaces a real need — not preemptively.

🤖 Generated with Claude Code

https://claude.ai/code/session_01GZEqXTAe8gSu3mHwc7qupv

chiptus · 2026-09-17T14:21:31Z

@@ -0,0 +1,59 @@
+---
+name: setup-chiptus-env
+description: "Configure this repo end to end: check setup-matt-pocock-skills is installed (asking the dev to install it if not), run it for the issue tracker / triage labels / domain docs, optionally relocate docs/agents/ (and domain docs) to a separate docs repo pointed to by an env var — reachable from both local sessions and cloud Routines — then scaffold the autonomic issue pipeline (triage sweep + fix worker Routines) wired to whichever tracker was chosen. Run once per repo before relying on the autonomic pipeline."


I think the description can be shorter

chiptus · 2026-09-17T15:15:37Z

+
+Check for a `setup-matt-pocock-skills` folder under `.claude/skills/` or `.agents/skills/` — locally, or globally per whatever install location the dev is using (ask if unclear). Present → continue to step 2.
+
+Missing → **don't install it yourself.** How and where to install it (per-repo vs. global machine-wide, plugin vs. `npx skills add`) is the dev's call, not this skill's — installing on their behalf risks the wrong scope or clobbering an existing setup. Tell the dev it's missing, give them the install command (`npx skills add <setup-matt-pocock-skills package> -s "*" -a claude-code -y --json` — note the agent identifier is `claude-code`, not `claude`; the latter is rejected by the CLI) or point at the plugin marketplace flow, and stop. Resume at step 2 once they confirm it's installed.


Do we really need this? Just tell the user it's needed and let him install whatever way he prefers

chiptus · 2026-09-23T18:44:18Z

+
+1. **Tests for the change**: a test-less PR is acceptable only for pure chores.
+2. **Local checks pass before every push**: this repo's lint and unit-test commands, plus affected integration tests.
+3. **CI green on the PR head**, with review-bot findings addressed via the `pr-review-fixer` skill — bot/automated review comments only; a maintainer's own comment on the PR is his, per the repair-before-build guardrail above, never something this gate auto-fixes.


this is not needed from the bot. the dev will invoke this later

Moved from chiptus/UpLine PR mattpocock#499 so it's installable across repos via npx skills / the Claude Code plugin, not just usable inside UpLine. Registers the skill in .claude-plugin/plugin.json and skills/chiptus/README.md. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GZEqXTAe8gSu3mHwc7qupv

Installing on the dev's behalf risks the wrong scope (per-repo vs global) or clobbering an existing setup. The skill now checks and, if missing, hands the dev the install command and stops, rather than running npx skills itself. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GZEqXTAe8gSu3mHwc7qupv

Fix firing step 6 depends on the create-pr skill to open the PR; a missing create-pr previously wasn't caught until the last step of a firing, after all the implementation work was already done. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GZEqXTAe8gSu3mHwc7qupv

Quality gate 3 (address review-bot findings before flagging a fix PR for review) is pr-review-fixer's job. Name it as a prerequisite alongside triage/implement/create-pr, and scope its use in the gate to bot findings only -- a maintainer's own review comment stays untouched, per the repair-before-build guardrail already in place. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GZEqXTAe8gSu3mHwc7qupv

…ore-overwrite autonomic-issues.md is a generic template refreshed in place; repo-specific guardrails, CLI examples, and rubric mechanics now belong in a separate docs/agents/autonomic-issues-local.md that a refresh never reads or writes. Step 7 also diffs against an existing autonomic-issues.md before overwriting it, instead of blindly template-stamping over it. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GZEqXTAe8gSu3mHwc7qupv

…GENTS.md docs/agents/autonomic-issues.md is the source of truth and needs no always-loaded entry there; skip the "### Autonomic issue pipeline" block step 7 previously added. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GZEqXTAe8gSu3mHwc7qupv

* feat(skills): add setup-chiptus-env, ported from chiptus/UpLine Moved from chiptus/UpLine PR mattpocock#499 so it's installable across repos via npx skills / the Claude Code plugin, not just usable inside UpLine. Registers the skill in .claude-plugin/plugin.json and skills/chiptus/README.md. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GZEqXTAe8gSu3mHwc7qupv * fix(setup-chiptus-env): ask, don't auto-install setup-matt-pocock-skills Installing on the dev's behalf risks the wrong scope (per-repo vs global) or clobbering an existing setup. The skill now checks and, if missing, hands the dev the install command and stops, rather than running npx skills itself. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GZEqXTAe8gSu3mHwc7qupv * fix(setup-chiptus-env): also check create-pr is installed Fix firing step 6 depends on the create-pr skill to open the PR; a missing create-pr previously wasn't caught until the last step of a firing, after all the implementation work was already done. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GZEqXTAe8gSu3mHwc7qupv * fix(setup-chiptus-env): also check pr-review-fixer is installed Quality gate 3 (address review-bot findings before flagging a fix PR for review) is pr-review-fixer's job. Name it as a prerequisite alongside triage/implement/create-pr, and scope its use in the gate to bot findings only -- a maintainer's own review comment stays untouched, per the repair-before-build guardrail already in place. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GZEqXTAe8gSu3mHwc7qupv * feat(setup-chiptus-env): add repo-specific extension point + diff-before-overwrite autonomic-issues.md is a generic template refreshed in place; repo-specific guardrails, CLI examples, and rubric mechanics now belong in a separate docs/agents/autonomic-issues-local.md that a refresh never reads or writes. Step 7 also diffs against an existing autonomic-issues.md before overwriting it, instead of blindly template-stamping over it. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GZEqXTAe8gSu3mHwc7qupv * fix(setup-chiptus-env): don't write a pipeline pointer to CLAUDE.md/AGENTS.md docs/agents/autonomic-issues.md is the source of truth and needs no always-loaded entry there; skip the "### Autonomic issue pipeline" block step 7 previously added. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GZEqXTAe8gSu3mHwc7qupv --------- Co-authored-by: Claude <noreply@anthropic.com>

chiptus mentioned this pull request Sep 17, 2026

feat(skills): add setup-chiptus-env (needs discussion) chiptus/UpLine#499

Closed

chiptus commented Sep 23, 2026

View reviewed changes

claude added 5 commits September 23, 2026 18:45

chiptus force-pushed the feat/setup-chiptus-env branch from ab48f93 to 57d1986 Compare September 23, 2026 18:45

chiptus merged this pull request into main Sep 28, 2026

Navigation Menu

Repository navigation

feat(skills): add setup-chiptus-env - #6

feat(skills): add setup-chiptus-env#6
chiptus merged 6 commits into
mainfrom
feat/setup-chiptus-env

chiptus commented Sep 16, 2026 •

edited

Loading

Uh oh!

chiptus Sep 17, 2026

Uh oh!

chiptus Sep 17, 2026

Uh oh!

chiptus Sep 23, 2026

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants


		Check for a `setup-matt-pocock-skills` folder under `.claude/skills/` or `.agents/skills/` — locally, or globally per whatever install location the dev is using (ask if unclear). Present → continue to step 2.

		Missing → don't install it yourself. How and where to install it (per-repo vs. global machine-wide, plugin vs. `npx skills add`) is the dev's call, not this skill's — installing on their behalf risks the wrong scope or clobbering an existing setup. Tell the dev it's missing, give them the install command (`npx skills add <setup-matt-pocock-skills package> -s "*" -a claude-code -y --json` — note the agent identifier is `claude-code`, not `claude`; the latter is rejected by the CLI) or point at the plugin marketplace flow, and stop. Resume at step 2 once they confirm it's installed.

Conversation

chiptus commented Sep 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Verification

Uh oh!

chiptus Sep 17, 2026

Choose a reason for hiding this comment

Uh oh!

chiptus Sep 17, 2026

Choose a reason for hiding this comment

Uh oh!

chiptus Sep 23, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

chiptus commented Sep 16, 2026 •

edited

Loading