Skip to content

Pro ​

The kit comes in two editions. Community carries the whole process including the runner. Pro covers what was created since v5.4.0 or carries operation in a company. Edition and version are named by the installer at the end and by /session-start, in Pro also by ./doctor.sh.

Community ​

  • the skills and the process description
  • the board with GitHub, GitLab, Kanban and local
  • the check before the commit with commit lock
  • push main and merge production, push main taking the full route with the check run
  • the runner: run, chain, check run, the pass for one card and preparing push main
  • choosing the model per task tier
  • several review models with pairings and review stages, also in /issue-review
  • the cost budget of the implementation
  • the evaluations of effort, effectiveness and findings, the comparison of the check areas
  • the reports of the runner and of interactive sessions to the control center (Leitstand)
  • the installer, also for updating

Pro ​

  • The desktop app including the settings interface.
  • doctor, the check of the setup.
  • The reminder of a new version.
  • ./update.sh and ./update-all.sh including the list of projects.
  • The deployment tool and its reporting to the control center.
  • Simultaneous packages including the slots for full check runs per machine.
  • The card check (Prüfung je Karte) including the repair loop with kit:repair, and push main in one step: every finished card comes to the check by itself, with a build service on one check branch per machine, and push main publishes the commit it has checked green. The desktop app shows at the top of every page the result of the check and, separately, whether publishing is possible, and reports the end of a check. The boundary is the Pro part card-check; without it a run ends with the integration run.
  • Planned: the adapters for Jira and Azure DevOps.
  • Hotfix and rollback, hotfix production and rollback production.

Pro calls in Community ​

In Community a Pro call answers with a sentence like this one and changes nothing:

Die Desktop-App gehört zu Pro, dem Teil des Kits für den Betrieb im Unternehmen. Mehr dazu und Kontakt: https://docs.mwolff.org/pro

In an English project the sentence reads The desktop app is part of Pro, … and points to https://docs.mwolff.org/en/pro. If the config holds night.concurrentPackages, KIT_FULL_CHECKS_MAX or KIT_FULL_CHECKS_DIR, the runner in Community implements the packages one after another and names them in one line per run. hotfixMinutes and runsInstance have no effect in Community either.

License ​

Community is under MIT, Pro under FSL-1.1-MIT; every installation brings the license text of its edition along. The versions published up to v5.4.0 remain under GPL v3.

Getting Pro ​

You get Pro through Manfred Wolff: info@mwolff.org, mwolff.org. The license gives you read access to the private repository mannewolff/claude-workflow-kit-pro. You fetch the installer in the project folder with a signed-in gh:

bash
gh api 'repos/mannewolff/claude-workflow-kit-pro/contents/install.mjs?ref=production' -H 'Accept: application/vnd.github.raw' > install.mjs && node install.mjs

Without gh the kit takes a read token from KIT_PRO_TOKEN. A Community project, a 5.x project as well, switches to Pro only through this call.

claude-workflow-kit — freely available