Microsoft/bcquality
1
0
Fork 0
mirror of https://github.com/microsoft/BCQuality.git synced 2026-10-05 14:46:55 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

Merge pull request #58 from Curabis/setup/auto-onboarding-selfheal

Browse source 
Auto-onboarding: kloning af et CURABIS-repo onboarder maskinen selv (setup v15)
This commit is contained in:
Michael Dieringer 2026-07-03 15:40:32 +02:00 • committed by GitHub
commit 0f80d267b5
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 20 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

7
CONSUMPTION.md
View file

@ -51,6 +51,13 @@ personal client secret), the knowledge sync script, and syncs the machine
mirror. Per repo afterwards: VS Code → `AL: Configure MCP Server` (generates
`.vscode/find-altool.ps1`), then "Opdater CURABIS Standard fra BCQuality".
**Auto-trigger:** the command above rarely needs to be run by hand. Every
project CLAUDE.md (setup v15+) carries a machine self-heal: any Claude Code
session in any configured CURABIS repo detects an un-onboarded machine
(missing `~/.claude/CLAUDE.md` or bridge) and runs the onboarding itself —
cloning a CURABIS repo IS the onboarding. Only the personal client secret
and the VS Code AL extension remain manual by design.
## Release channel: `stable`
Merging to `main` is **not** a deployment. All consumers — the machine

19
custom/setup/curabis-standard.agent.md
View file

@ -1,7 +1,7 @@
---
kind: action-skill
id: curabis-standard-setup
version: 14
version: 15
title: CURABIS Standard — Project Setup
description: >
Configures a new or existing repository to the CURABIS Standard development
@ -185,14 +185,21 @@ to this repository (BCQuality rule
`bcquality-knowledge-must-mirror-to-machine-not-repo`) — one sync per machine
covers every repo, and the repo history stays free of upstream rule churn.
If `~/.claude/bcquality-knowledge/` is missing or empty, self-heal before continuing:
**Machine self-heal (auto-onboarding):** if this machine is not CURABIS-
onboarded — `~/.claude/CLAUDE.md` or `~/.claude/bc-mcp-bridge.js` is missing —
run the full onboarding NOW (idempotent; identity taken from git config):
powershell -ExecutionPolicy Bypass -Command "Invoke-WebRequest -UseBasicParsing https://raw.githubusercontent.com/Curabis/BCQuality/stable/custom/setup/machine/Install-CurabisMachine.ps1 -OutFile $env:TEMP\icm.ps1; & $env:TEMP\icm.ps1"
Then report the manual leftovers it lists (personal client secret, AL:
Configure MCP Server) and ask the developer to restart Claude Code.
If only `~/.claude/bcquality-knowledge/` is missing or stale, the lighter
self-heal suffices:
powershell -ExecutionPolicy Bypass -File "$env:USERPROFILE\.claude\sync-bcquality-knowledge.ps1"
If the sync script itself is missing, first download it AS RAW BYTES (do not
decode/re-encode — use `Invoke-WebRequest -OutFile`) from
`https://raw.githubusercontent.com/Curabis/BCQuality/stable/custom/setup/sync-bcquality-knowledge.ps1`
to `~/.claude/sync-bcquality-knowledge.ps1`, then run it.
(If that sync script itself is missing, the full onboarding above installs it.)
These rules are always active.