kiln-cli 0.3.2__tar.gz → 0.3.3__tar.gz

kiln_cli-0.3.3/.pre-commit-config.yaml

@@ -0,0 +1,31 @@
+# Contrôles de kiln rejoués par git, comme dans les repos générés.
+#
+# Installation, une fois, à la racine : kiln install  (ou : uvx pre-commit install)
+# Le crochet vaut pour l'arbre principal et tous les worktrees. Tout rejouer :
+#   pre-commit run --all-files --hook-stage pre-push
+# Le typage, trop lent pour chaque commit, se joue avant chaque push : `develop` ne reçoit la
+# CI complète qu'au passage d'une version (skill `base:version`).
+default_install_hook_types: [pre-commit, pre-push]
+default_stages: [pre-commit]
+repos:
+  - repo: local
+    hooks:
+      - id: ruff-check
+        name: ruff check
+        entry: uv run ruff check --fix --force-exclude
+        language: system
+        types: [python]
+
+      - id: ruff-format
+        name: ruff format
+        entry: uv run ruff format --force-exclude
+        language: system
+        types: [python]
+
+      - id: typage
+        name: typage mypy (avant push)
+        entry: uv run mypy src tests
+        language: system
+        pass_filenames: false
+        always_run: true
+        stages: [pre-push]

{kiln_cli-0.3.2 → kiln_cli-0.3.3}/CHANGELOG.md

@@ -5,6 +5,11 @@ changement visible (`- …`), cassants en tête. `kiln update` montre les entré
 qu'un projet passe ; la skill `base:version` rédige celle de la version qu'elle sort, sur la
 branche `release/vX.Y.Z`, avant sa première candidate.
 
+## v0.3.3 — 2026-10-16
+- `kiln completion bash` : script de complétion tiré des commandes et options de kiln, à activer par `eval "$(kiln completion bash)"` dans `~/.bashrc` (#41, merci @HarshRajSinghania).
+- Skill `good-first-issues` : garde ouvertes sur GitHub quelques issues pour débutants, tirées du backlog et réservées aux contributeurs extérieurs.
+- Correctifs : `kiln update` ne s'arrête plus sur un conflit dans `ci.yml` après la promotion d'une version (seul le `@<tag>` des workflows de kiln différait) ; `base:worktree` ne bute plus sur un repo sans fichier `.env` ; la mise à jour d'un kiln installé depuis un dossier retire aussi l'ancien outil `kiln`.
+
 ## v0.3.2 — 2026-10-16
 - `kiln adopt` fait suivre kiln à un repo existant, sans le régénérer ; le skill `adoption` trie avec l'utilisateur ce que la charte y trouve à redire, et l'ouverture de session le propose dans un repo à soi qui ne suit pas encore kiln.
 - Dérogations à la charte dans `kiln-waivers.toml`, avec un motif et une échéance croissante à chaque renouvellement : `kiln waive` les ajoute, renouvelle ou liste, `kiln update` épargne les fichiers figés et dit ce qu'il y aurait changé, `kiln status` compte celles de chaque repo.

{kiln_cli-0.3.2 → kiln_cli-0.3.3}/CLAUDE.md

@@ -27,7 +27,8 @@ un dossier ou un module.
   (skills `worktree`, `fusion`, `version`, `nettoyage`, `relecture` (commits et diff d'une branche avant la fusion, dépôt entier avant une version), `backlog`, `maj-kiln`, `adoption`,
   `report-to-kiln` (défaut de kiln remonté en issue ou PR), `token` (jeton d'un service dans
   `.<service>/`), `contribution` (PR d'un contributeur extérieur : sécurité, tri, revue,
-  fusion créditée) ; `hooks/` (dont `relances.py`, politique commune des questions de kiln) ; `scripts/statusline.py`),
+  fusion créditée), `good-first-issues` (quelques issues pour débutants tirées du backlog,
+  réservées aux contributeurs extérieurs) ; `hooks/` (dont `relances.py`, politique commune des questions de kiln) ; `scripts/statusline.py`),
   `pile-django/`, `pile-nuxt/`, `vps-podman/`, `stripe/`, `serena/`.
 - `.github/workflows/` : workflows réutilisables appelés par les repos générés, plus ceux de
   kiln (`kiln.yml` contrôles, `pypi.yml` publication du paquet `kiln-cli` au tag promu) ;
@@ -98,5 +99,6 @@ l'outil), `release.py` (`kiln version`).
 
 `uv run pytest -q` (réparti sur tous les cœurs par pytest-xdist : une vingtaine de secondes ;
 `-n 0` pour un seul processus, au débogage), `uv run ruff check`
-et `uv run ruff format --check`. Un hook ou un script de plugin est lu en direct par Claude Code
+et `uv run ruff format --check`. Le crochet pre-commit de kiln (`.pre-commit-config.yaml`, posé par
+`kiln install`) lance ruff à chaque commit et mypy avant chaque push. Un hook ou un script de plugin est lu en direct par Claude Code
 (catalogue déclaré en dossier local) : il agit dès la fusion dans `develop`.

{kiln_cli-0.3.2 → kiln_cli-0.3.3}/CONTRIBUTING.md

@@ -33,6 +33,7 @@ You need [uv](https://docs.astral.sh/uv/) and git. Python 3.14 is downloaded by
 git clone https://github.com/antoine-tena/kiln
 cd kiln
 uv sync
+uvx pre-commit install           # ruff before each commit, mypy before each push
 uv run kiln                      # the CLI, straight from your checkout
 KILN_TEMPLATE=$PWD uv run kiln new /tmp/demo --no-github   # try your template changes
 ```
@@ -42,7 +43,7 @@ Checks (the same ones CI runs):
 ```sh
 uv run ruff check . && uv run ruff format --check src tests
 uv run mypy src tests
-uv run pytest -q                 # renders every stack combination, takes ~2 minutes
+uv run pytest -q                 # renders every stack combination, ~20 s on all cores
 ```
 
 ## Where things live

{kiln_cli-0.3.2 → kiln_cli-0.3.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: kiln-cli
-Version: 0.3.2
+Version: 0.3.3
 Summary: Make Claude Code build production-grade repos, and keep them that way
 Project-URL: Homepage, https://github.com/antoine-tena/kiln
 Project-URL: Changelog, https://github.com/antoine-tena/kiln/blob/develop/CHANGELOG.md
@@ -78,6 +78,7 @@ keeps every repo you own current:
 #    macOS, Linux, and Windows through WSL. The PyPI package is kiln-cli, the command is kiln.
 uv tool install kiln-cli
 #    …or try it without installing anything: uvx kiln-cli new my-app
+#    Tab completion in bash: add  eval "$(kiln completion bash)"  to ~/.bashrc
 
 # 2. Create a project — answer a few questions, or pass them as flags
 kiln new my-app
@@ -168,6 +169,7 @@ make the opinions yours.
 | `kiln doctor` | Check the machine (git, uv, gh login, pnpm, podman, Java, pre-commit, kiln release, Claude plugin) and the current repo; each problem comes with the command that fixes it. Changes nothing. |
 | `kiln ci [commit]` | Replay the repo's GitHub CI locally against throwaway PostgreSQL/Redis, and push the verdict as a git note. |
 | `kiln contrat` | Django + Nuxt: export `openapi.json` and regenerate the front's API types. |
+| `kiln completion bash` | Print a bash completion script built from the parser; enable it with `eval "$(kiln completion bash)"` in `~/.bashrc`. |
 | `charte` | Check the repo against its `charte.toml` (`--detail`, `types`, `couverture`). |
 
 Full reference (in French): [README.fr.md](README.fr.md#commandes).
@@ -198,7 +200,7 @@ claude plugin install base@kiln
 
 | Plugin | What's inside |
 |---|---|
-| `base` | Skills for the git workflow (`worktree`, `fusion` = merge, `version` = release, `nettoyage` = cleanup, `relecture` = review of a branch's commits before they go public, and of the whole repo before a release, `backlog`, `maj-kiln` = self-update, `adoption` = bring an existing repo under kiln), `report-to-kiln` (a kiln defect met in your repo becomes an issue or a PR, posted once you approve) `contribution` (an outside contributor's PR handled like a well-run open-source project: untrusted code read before anything runs, triage, review, a merge that credits them, nothing posted without your yes) and `token` (a service token pasted once into a git-ignored `.<service>/` folder, never shown); hooks that guard protected branches and files, refuse a commit message signed by Claude, check each edited file, and ask at session start: kiln updates in kiln repos, adoption in your other repos ("Yes", "Later", "Never for this repo"), all paced by one goodwill score that each yes raises and each no lowers; a shared status line in four styles (`kiln set statusline=…`, or `aucune` / `perso` to keep your own); condensed command output with [rtk](https://github.com/rtk-ai/rtk). |
+| `base` | Skills for the git workflow (`worktree`, `fusion` = merge, `version` = release, `nettoyage` = cleanup, `relecture` = review of a branch's commits before they go public, and of the whole repo before a release, `backlog`, `maj-kiln` = self-update, `adoption` = bring an existing repo under kiln), `report-to-kiln` (a kiln defect met in your repo becomes an issue or a PR, posted once you approve) `contribution` (an outside contributor's PR handled like a well-run open-source project: untrusted code read before anything runs, triage, review, a merge that credits them, nothing posted without your yes), `good-first-issues` (a small, steady stock of `good first issue` issues drawn from your backlog and reserved for newcomers, refilled as they get merged) and `token` (a service token pasted once into a git-ignored `.<service>/` folder, never shown); hooks that guard protected branches and files, refuse a commit message signed by Claude, check each edited file, and ask at session start: kiln updates in kiln repos, adoption in your other repos ("Yes", "Later", "Never for this repo"), all paced by one goodwill score that each yes raises and each no lowers; a shared status line in four styles (`kiln set statusline=…`, or `aucune` / `perso` to keep your own); condensed command output with [rtk](https://github.com/rtk-ai/rtk). |
 | `pile-django` | Migrations, API regeneration, read-only PostgreSQL. |
 | `pile-nuxt` | Nuxt / Vue / Vitest skills, UI polish, screenshots on three phones and a desktop (Playwright). |
 | `vps-podman` | Deploy, production logs, production dumps. |

{kiln_cli-0.3.2 → kiln_cli-0.3.3}/README.fr.md

@@ -32,7 +32,7 @@ Les plugins Claude Code vivent dans [`plugins/`](plugins/), catalogue `kiln`
 - `base`, pour tous les projets, installé au niveau utilisateur : skills `worktree`, `fusion`,
   `version` (release/vN, contrôle complet, annonce, main tagué, déploiement), `nettoyage`,
   `relecture` (commits et diff d'une branche relus et rangés avant la fusion, dépôt entier avant une version), `backlog`,
-  `maj-kiln` (l'outil kiln et ses plugins, puis le repo ouvert), `adoption` (`kiln adopt` dans un repo existant, passif de la charte trié avec l'utilisateur), `report-to-kiln` (un défaut de kiln remonté en issue ou en PR, avec l'accord de l'utilisateur), `contribution` (la PR d'un contributeur extérieur : code relu avant d'en rien lancer, tri, revue, fusion qui le crédite, rien publié sans accord) ; hooks garde de branche (et refus d'un message de commit signé Claude), fichiers protégés, contrôle du fichier
+  `maj-kiln` (l'outil kiln et ses plugins, puis le repo ouvert), `adoption` (`kiln adopt` dans un repo existant, passif de la charte trié avec l'utilisateur), `report-to-kiln` (un défaut de kiln remonté en issue ou en PR, avec l'accord de l'utilisateur), `contribution` (la PR d'un contributeur extérieur : code relu avant d'en rien lancer, tri, revue, fusion qui le crédite, rien publié sans accord), `good-first-issues` (un petit stock d'issues `good first issue` tiré du backlog et réservé aux contributeurs extérieurs, regarni à chaque fusion) ; hooks garde de branche (et refus d'un message de commit signé Claude), fichiers protégés, contrôle du fichier
   modifié, questions à l'ouverture de session : dans un repo kiln, sa mise à jour (l'outil kiln s'il
   est en retard sur GitHub, puis le repo par `kiln update` ; un « non » repousse la question de
   5, 10, 30 puis 50 sessions, après quoi désinstaller kiln ou délier le repo est proposé) ; dans
@@ -80,6 +80,7 @@ l'installer). Pour suivre les candidates (canal `interne`) ou un commit précis
 `uv tool install git+https://github.com/antoine-tena/kiln@<tag>`. macOS, Linux, et Windows par
 WSL. Quand une version sort, le hook de début de session propose de mettre à jour l'outil, puis
 chaque repo ; à la main : `uv tool upgrade kiln-cli`, puis `kiln update` dans le repo.
+Complétion dans bash : `eval "$(kiln completion bash)"` dans `~/.bashrc`.
 Python 3.14 est requis ; uv le télécharge au besoin. Au premier `kiln install`, kiln demande le
 système du poste (Linux, WSL ou macOS) et le garde dans `~/.config/kiln/config.toml`, avec
 `proprietaire` et `equipe` par défaut si on les y ajoute.
@@ -100,6 +101,7 @@ système du poste (Linux, WSL ou macOS) et le garde dans `~/.config/kiln/config.
 | `kiln update` | Évolutions du modèle, mises à jour compatibles des dépendances, puis contrôles. `--major` : versions majeures comprises. `--no-template`, `--no-deps` pour n'en faire qu'une partie. |
 | `kiln update --all` | Tous les repos kiln du dossier de code (`~/code`, réglable par `dossier_code`) : pour chacun, un worktree depuis la branche d'intégration, la mise à jour, des commits de dix fichiers au plus, puis la fusion directe dans l'intégration (commit de fusion poussé) ; contrôles en échec, la branche est poussée sans être fusionnée. L'arbre principal ne change jamais de branche. |
 | `kiln doctor` | Diagnostic du poste (git, uv, gh connecté, pnpm, podman, Java, pre-commit, version de kiln, plugin Claude, configuration) et du repo courant (version du modèle, crochet pre-commit, dépendances, `backend/.env`) : ✓, ! à regarder ou ✗ bloquant, chaque fois avec la commande qui corrige. Ne modifie rien. |
+| `kiln completion bash` | Script de complétion bash tiré des commandes et options de kiln ; l'activer par `eval "$(kiln completion bash)"` dans `~/.bashrc`. |
 | `kiln status` | État des repos kiln du dossier de code : branche, arbre propre ou non, version du modèle (`v0.3.2 → v0.3.5` en retard), dérogations (`!` si l'une est échue), stack ; puis les règles dérogées, par nombre de repos. |
 | `kiln version` | Dans le dépôt de kiln : dernière version publique, candidates (âge, repos qui les ont adoptées, prêtes à promouvoir) et numéro de la prochaine. |
 | `charte` | Vérifie le repo contre son `charte.toml` (`charte --detail`, `charte types`, `charte couverture`). |

{kiln_cli-0.3.2 → kiln_cli-0.3.3}/README.md

@@ -54,6 +54,7 @@ keeps every repo you own current:
 #    macOS, Linux, and Windows through WSL. The PyPI package is kiln-cli, the command is kiln.
 uv tool install kiln-cli
 #    …or try it without installing anything: uvx kiln-cli new my-app
+#    Tab completion in bash: add  eval "$(kiln completion bash)"  to ~/.bashrc
 
 # 2. Create a project — answer a few questions, or pass them as flags
 kiln new my-app
@@ -144,6 +145,7 @@ make the opinions yours.
 | `kiln doctor` | Check the machine (git, uv, gh login, pnpm, podman, Java, pre-commit, kiln release, Claude plugin) and the current repo; each problem comes with the command that fixes it. Changes nothing. |
 | `kiln ci [commit]` | Replay the repo's GitHub CI locally against throwaway PostgreSQL/Redis, and push the verdict as a git note. |
 | `kiln contrat` | Django + Nuxt: export `openapi.json` and regenerate the front's API types. |
+| `kiln completion bash` | Print a bash completion script built from the parser; enable it with `eval "$(kiln completion bash)"` in `~/.bashrc`. |
 | `charte` | Check the repo against its `charte.toml` (`--detail`, `types`, `couverture`). |
 
 Full reference (in French): [README.fr.md](README.fr.md#commandes).
@@ -174,7 +176,7 @@ claude plugin install base@kiln
 
 | Plugin | What's inside |
 |---|---|
-| `base` | Skills for the git workflow (`worktree`, `fusion` = merge, `version` = release, `nettoyage` = cleanup, `relecture` = review of a branch's commits before they go public, and of the whole repo before a release, `backlog`, `maj-kiln` = self-update, `adoption` = bring an existing repo under kiln), `report-to-kiln` (a kiln defect met in your repo becomes an issue or a PR, posted once you approve) `contribution` (an outside contributor's PR handled like a well-run open-source project: untrusted code read before anything runs, triage, review, a merge that credits them, nothing posted without your yes) and `token` (a service token pasted once into a git-ignored `.<service>/` folder, never shown); hooks that guard protected branches and files, refuse a commit message signed by Claude, check each edited file, and ask at session start: kiln updates in kiln repos, adoption in your other repos ("Yes", "Later", "Never for this repo"), all paced by one goodwill score that each yes raises and each no lowers; a shared status line in four styles (`kiln set statusline=…`, or `aucune` / `perso` to keep your own); condensed command output with [rtk](https://github.com/rtk-ai/rtk). |
+| `base` | Skills for the git workflow (`worktree`, `fusion` = merge, `version` = release, `nettoyage` = cleanup, `relecture` = review of a branch's commits before they go public, and of the whole repo before a release, `backlog`, `maj-kiln` = self-update, `adoption` = bring an existing repo under kiln), `report-to-kiln` (a kiln defect met in your repo becomes an issue or a PR, posted once you approve) `contribution` (an outside contributor's PR handled like a well-run open-source project: untrusted code read before anything runs, triage, review, a merge that credits them, nothing posted without your yes), `good-first-issues` (a small, steady stock of `good first issue` issues drawn from your backlog and reserved for newcomers, refilled as they get merged) and `token` (a service token pasted once into a git-ignored `.<service>/` folder, never shown); hooks that guard protected branches and files, refuse a commit message signed by Claude, check each edited file, and ask at session start: kiln updates in kiln repos, adoption in your other repos ("Yes", "Later", "Never for this repo"), all paced by one goodwill score that each yes raises and each no lowers; a shared status line in four styles (`kiln set statusline=…`, or `aucune` / `perso` to keep your own); condensed command output with [rtk](https://github.com/rtk-ai/rtk). |
 | `pile-django` | Migrations, API regeneration, read-only PostgreSQL. |
 | `pile-nuxt` | Nuxt / Vue / Vitest skills, UI polish, screenshots on three phones and a desktop (Playwright). |
 | `vps-podman` | Deploy, production logs, production dumps. |

{kiln_cli-0.3.2 → kiln_cli-0.3.3}/docs/backlog/backlog.md

@@ -22,7 +22,7 @@ North star: **kiln v0.3.0 public, adopted by every generated repo**.
     Why, what to do (as a `- [ ]` checklist when there are several steps), where to look.
 
 - **ID** `T-NN`: stable, never reused, quoted as is in commits and branches (tickets opened
-  before 16 October 2026 were `AF-NN`, same number). **Next free: T-18.**
+  before 16 October 2026 were `AF-NN`, same number). **Next free: T-22.**
 - **Type**, one of: `bug` (something is broken); `improvement` (it works, it could work
   better); `idea` (nothing exists yet, to be explored); `task` (work that is neither: a release,
   a decision, a check).
@@ -36,6 +36,8 @@ North star: **kiln v0.3.0 public, adopted by every generated repo**.
   log: `- **YYYY-MM-DD** · T-NN · Title — what was done (branch) · opened YYYY-MM-DD`.
 - **Locations quoted are hints, not addresses.**
 - Overview: `grep -E '^(## |### T-|- \*\*Status)' docs/backlog/backlog.md`.
+- **Good first issues**: keep 3 open on GitHub, reserved for outside contributors (skill
+  `base:good-first-issues`); their tickets have **Owner**: `contributor — #NN`.
 
 ---
 
@@ -43,20 +45,21 @@ North star: **kiln v0.3.0 public, adopted by every generated repo**.
 
 ### T-14 · Promote v0.3.1, the first release on PyPI
 - **Type**: task
-- **Status**: blocked — waiting for `v0.3.2-rc.1`
+- **Status**: blocked — waiting for antoine (delete the old token)
 - **Opened**: 2026-10-16
-- **Effort**: S · **Owner**: Claude · **Due**: —
+- **Effort**: XS · **Owner**: antoine, then Claude · **Due**: —
 - **Origin**: promotion of v0.3.0, 16 October 2026
 
-`v0.3.0` has no PyPI workflow: `kiln-cli` is first published when `v0.3.1` is promoted. The
-`PYPI_TOKEN` secret (environment `pypi`, account-wide token in `.pypi/token`) is set.
-- [ ] Cut `v0.3.2-rc.1` from `develop`; its `CHANGELOG.md` entry credits the first outside
-  contribution: `kiln --version` (#39, thanks @SakarPaisen). Then `kiln update --all`.
-- [ ] Promote `v0.3.1` (tag on the commit of `v0.3.1-rc.1`, merge into `main`, back into
-  `develop`), check the `pypi` run, then `uv tool install kiln-cli` on a clean machine.
-- [ ] Replace the account-wide token with one scoped to `kiln-cli`
-  (https://pypi.org/manage/project/kiln-cli/settings/), update the secret, delete the old one.
-- [ ] README (English and French): `uv tool install kiln-cli` as the main install.
+`v0.3.1` is promoted and `kiln-cli 0.3.1` is on PyPI (16 October 2026); `v0.3.2-rc.2` is the
+candidate followed by annway, sweep and vision.
+- [x] Cut `v0.3.2-rc.1`, then `-rc.2` (tests independent of the machine's git config); the
+  `CHANGELOG.md` entry credits #39 (@SakarPaisen). `kiln update --all` done.
+- [x] Promote `v0.3.1`, `pypi` run green, `uvx --from kiln-cli==0.3.1 kiln` works on an empty
+  uv cache.
+- [x] README (English and French): `uv tool install kiln-cli` as the main install.
+- [x] Token scoped to `kiln-cli` in `.pypi/token`, `PYPI_TOKEN` secret updated (16 October
+  2026); it is first used by the promotion of `v0.3.2`.
+- [ ] antoine deletes the old account-wide token on https://pypi.org/manage/account/token/
 
 ## 🟠 Important
 
@@ -69,7 +72,14 @@ North star: **kiln v0.3.0 public, adopted by every generated repo**.
   16 October 2026
 
 antoine's goal: lots of stars. Directories take projects that already have users: the launch
-comes first. Posts are made by antoine, never without them; Claude drafts the texts.
+comes first. Hacker News and Reddit: posted by antoine (no API for HN, Reddit vets new apps),
+Claude drafts the texts. Elsewhere, Claude posts directly on antoine's accounts, with no review
+(antoine's call, 16 October 2026), saying the text is written with Claude where the platform
+asks, then gives the links.
+- [x] Accounts with an API key, ready (16 October 2026): dev.to (`.devto/`, user
+  `antoine-tena`) and Bluesky (`.bluesky/`, `antoine-tena.bsky.social`, app password).
+- [ ] On launch day: article on dev.to, post on Bluesky (Mastodon dropped, antoine's call,
+  16 October 2026).
 - [ ] A demo of `kiln new` at the top of the README (GIF or asciinema, issue #38).
 - [ ] Show HN (https://news.ycombinator.com/submit), suggested title "Show HN: Kiln – make
   Claude Code build production-grade repos, and keep them that way".
@@ -207,12 +217,16 @@ takes the nested worktrees as gitlinks; `.claude/worktrees/` is only ignored in
 - **Effort**: S · **Owner**: Claude · **Due**: —
 - **Origin**: interface redesign, 15 October 2026
 - [ ] `kiln check`: the step title and the `✓` line say the same thing (one command per step).
-- [ ] Bash completion (`kiln <Tab>`).
+- Bash completion moved to T-20.
 
 ---
 
 ## ✅ Done
 
+- **2026-10-16** · T-21 · Credit #41 in the notes of the next release — line in the `v0.3.3` entry of `CHANGELOG.md` (release/v0.3.3) · opened 2026-10-16
+- **2026-10-16** · T-20 · Bash completion (`kiln completion bash`) — PR #41 by @HarshRajSinghania, fixed up and merged, issue #40 closed · opened 2026-10-16
+- **2026-10-16** · T-18 · Promoting a release makes `kiln update` conflict on `ci.yml` — cause confirmed (Copier's old render takes the promoted tag from `git describe`); the three-way merge is redone with the project's tag, reproduced in a test (fix/conflit-promotion) · opened 2026-10-16
+- **2026-10-16** · T-19 · kiln has no pre-push hook — `.pre-commit-config.yaml` (ruff at commit, mypy before push), set by `kiln install` (chore/pre-push-kiln) · opened 2026-10-16
 - **2026-10-16** · T-16 · A failed `kiln update --all` leaves a worktree that blocks the next
   run — a worktree with no change and no commit of its own is removed after the failure and
   before the next run; one with work in it is kept and named (`fix/update-reseau`) · opened 2026-10-16

{kiln_cli-0.3.2 → kiln_cli-0.3.3}/plugins/base/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "base",
-  "version": "0.11.0",
-  "description": "Pour tous les projets : worktrees, fusion, version, nettoyage, mise à jour de kiln, défauts remontés à kiln, PR de contributeurs, jetons de service, garde de branche, modèle kiln à jour, fichiers protégés, context7",
+  "version": "0.12.0",
+  "description": "Pour tous les projets : worktrees, fusion, version, nettoyage, mise à jour de kiln, défauts remontés à kiln, PR de contributeurs, issues pour débutants, jetons de service, garde de branche, modèle kiln à jour, fichiers protégés, context7",
   "author": {
     "name": "antoine-tena"
   }

{kiln_cli-0.3.2 → kiln_cli-0.3.3}/plugins/base/README.md

@@ -4,7 +4,8 @@ Vu depuis un repo par le lien `.claude/kiln`, créé à l'ouverture de chaque se
 git) : c'est le plugin tel qu'il tourne sur ce poste.
 
 - `skills/` : les skills `/base:…` (`worktree`, `fusion`, `version`, `nettoyage`, `backlog`,
-  `maj-kiln`, `report-to-kiln`, `token`, `contribution`).
+  `maj-kiln`, `report-to-kiln`, `token`, `contribution`,
+  `good-first-issues`).
 - `hooks/` : les hooks (`hooks.json` dit quand chacun se déclenche).
 - `scripts/` : la status line.
 

{kiln_cli-0.3.2 → kiln_cli-0.3.3}/plugins/base/hooks/kiln-a-jour.py

@@ -188,7 +188,11 @@ def tool_update_command(install: tuple[str, str] | None, tag: str) -> str:
         return f'{legacy}uv tool install --force "{PYPI_NAME}=={version}" && {plugins}'
     if install is None or install[0] in ("git", "pypi"):
         return f'{legacy}uv tool install --force "git+{KILN_GIT_URL}@{tag}" && {plugins}'
-    return f'git -C "{install[1]}" pull --ff-only && uv tool install --reinstall "{install[1]}"'
+    # L'ancien outil retiré après le pull : un pull refusé ne laisse pas le poste sans kiln.
+    return (
+        f'git -C "{install[1]}" pull --ff-only && {legacy}'
+        f'uv tool install --reinstall "{install[1]}"'
+    )
 
 
 # --- Repo : de quelle version du modèle part-il ? ---

{kiln_cli-0.3.2 → kiln_cli-0.3.3}/plugins/base/scripts/preparer-worktree.sh

@@ -9,7 +9,7 @@ main_tree="$(dirname "$(git -C "$worktree" rev-parse --path-format=absolute --gi
 
 # Fichiers .env* ignorés de l'arbre principal (hors exemples et node_modules), même chemin relatif.
 git -C "$main_tree" ls-files --others --ignored --exclude-standard -- '*.env' '*.env.*' '.env' '.env.*' \
-  | grep -vE '(^|/)node_modules/|\.(example|sample)$|^\.claude/worktrees/' \
+  | { grep -vE '(^|/)node_modules/|\.(example|sample)$|^\.claude/worktrees/' || true; } \
   | while read -r f; do
       mkdir -p "$worktree/$(dirname "$f")"
       cp -p "$main_tree/$f" "$worktree/$f"

{kiln_cli-0.3.2 → kiln_cli-0.3.3}/plugins/base/skills/backlog/SKILL.md

@@ -25,7 +25,8 @@ everything in it is old: check it against the current code before acting. Never
 archived report.
 
 **No argument**: propose the next 3 tickets in section order (critical first), following the
-north star in the header and skipping `blocked` tickets; for each, the ID, one sentence, the
+north star in the header and skipping `blocked` tickets and those reserved for outside
+contributors (**Owner**: `contributor — #NN`, skill `base:good-first-issues`); for each, the ID, one sentence, the
 effort, and the owner. List separately the blocked tickets waiting for the user themselves.
 Quickly check in the code that the ticket is not already done (the locations quoted are hints,
 often stale).

{kiln_cli-0.3.2 → kiln_cli-0.3.3}/plugins/base/skills/contribution/SKILL.md

@@ -169,6 +169,8 @@ branch (`develop` if it exists, else the default branch; retarget with
   (`base:version`), note it in the backlog (`base:backlog`) so it is not forgotten.
 - A first contribution that went well: suggest a next one if an issue labelled
   `good first issue` fits, in one line, without insisting.
+- The PR closed a `good first issue`: close its ticket in the backlog, crediting them, and
+  offer to open the next one (`base:good-first-issues`).
 - If the user wants to be quick next time, say what would have helped (a PR template line, a
   rule in `CONTRIBUTING.md`) and offer to add it.
 

kiln_cli-0.3.3/plugins/base/skills/good-first-issues/SKILL.md

@@ -0,0 +1,92 @@
+---
+name: good-first-issues
+description: Keep a small, steady stock of `good first issue` issues open on GitHub, drawn from the backlog and reserved for outside contributors, so a newcomer who wants to help always finds a task ready; nothing is posted without the user's yes. Use when the user asks for good first issues, wants to attract contributors, or when base:contribution has just merged a PR that closed one.
+argument-hint: "[target number | off]"
+---
+
+A good first issue does not bring contributors by itself; it is the open door for someone who
+already wants to help. A few that are clear and alive beat many that rot: the target is small
+(3 by default, never more than 5), and an issue nobody took in three months is better closed
+than left as a sign of a project nobody follows.
+
+## The setting
+
+It lives in the "How to use" section of `docs/backlog/backlog.md`, one line:
+
+    - **Good first issues**: keep 3 open on GitHub, reserved for outside contributors (skill
+      `base:good-first-issues`); their tickets have **Owner**: `contributor — #NN`.
+
+- No line: the repo does not do this. Say so and offer to start (`$ARGUMENTS` a number, or the
+  user's yes to 3); the line goes in on the work branch with the first issues.
+- `$ARGUMENTS` a number: change the target in the line. `off`: remove the line; the open issues
+  stay, their tickets go back to `**Owner**: Claude` only if the user says so.
+- A repo without `docs/backlog/backlog.md`: skill `base:backlog` first.
+
+## 1. Count what is open
+
+    gh issue list --label "good first issue" --state open --json number,title,assignees,createdAt,updatedAt,comments
+
+Match each issue to its ticket in the backlog (`**Owner**: contributor — #NN`) and fix any drift:
+- an issue closed or merged whose ticket is still open: close the ticket (`base:backlog done`),
+  crediting the contributor (`… — fixed by @login in #PR`);
+- an open issue with no ticket (opened by hand): fine, it counts;
+- an issue with no activity for three months and no one on it: propose closing it with a
+  kind word and giving the ticket back (`**Owner**: Claude`).
+
+An issue someone asked for or is assigned to still counts: it is taken, not done.
+
+## 2. Pick the tickets that fill the gap
+
+Missing = target − open. Pick that many tickets from `docs/backlog/backlog.md`, all sections,
+that a stranger can do without knowing the project:
+- effort `XS` or `S`, one subject, a clear notion of done;
+- the files to touch are few and can be named; no design decision left open;
+- no secret, server, account or access only the user has; nothing urgent (🔴 critical stays
+  ours: a contributor may take weeks);
+- not `blocked`, not `in progress`, not already reserved.
+
+Prefer variety (a bug, a doc fix, a small improvement) and what a newcomer learns the project
+from. Check in the code that each ticket is still to do. If fewer tickets fit than missing, say
+so: a smaller stock is better than a vague issue. A large ticket can be split in the backlog
+first (a new `T-NN` for the small part) when the split is obvious.
+
+## 3. Write the issues
+
+In English, for someone who has never seen the repo. Title: what to achieve, not the ticket's
+internal wording. Body:
+
+    <why it matters, two or three sentences>
+
+    ## What to do
+    - [ ] …
+
+    ## Where to look
+    - `path/to/file.py` — <what is there>
+
+    ## Done when
+    <the visible result, and the test that shows it>
+
+    New to the project? Read [CONTRIBUTING.md](https://github.com/<owner>/<repo>/blob/<default branch>/CONTRIBUTING.md);
+    ask anything here, there is no wrong question.
+
+No internal jargon (ticket IDs, French names of the repo's skills, decisions made in chat),
+no `@` of anyone, nothing about Claude. Labels: `good first issue`, plus `bug`, `enhancement`
+or `documentation` as fits (`gh label list`).
+
+## 4. Post, after the yes
+
+Show the user each title and body, say they will be public under their account, and post only
+after an explicit yes:
+
+    gh issue create --title "…" --body-file <file> --label "good first issue" --label "…"
+
+Then, on the work branch (a worktree, skill `base:worktree`), set each ticket's **Owner** to
+`contributor — #NN`, add the setting line if it was missing, commit
+(`docs(backlog): good first issues #NN, #NN`), and merge (`base:fusion`).
+
+## Reserved tickets
+
+A ticket whose **Owner** is `contributor — #NN` is left for outside contributors: never
+proposed as next (`base:backlog`), never fixed by us, even in ten minutes, even in passing.
+The exceptions are the user's decision: they need it now, or it turned out not to fit (then
+close the issue with an explanation and give the ticket back).

{kiln_cli-0.3.2 → kiln_cli-0.3.3}/pyproject.toml

@@ -1,7 +1,7 @@
 [project]
 # Sur PyPI, `kiln` est pris : la distribution s'appelle kiln-cli, la commande reste `kiln`.
 name = "kiln-cli"
-version = "0.3.2"
+version = "0.3.3"
 description = "Make Claude Code build production-grade repos, and keep them that way"
 readme = "README.md"
 license = "MIT"

{kiln_cli-0.3.2 → kiln_cli-0.3.3}/src/kiln/cli.py

@@ -42,7 +42,7 @@ FRONTENDS = ("nuxt", "next", "astro", "streamlit", "dash", "aucun")
 # Écran d'accueil : commandes par section ; le rôle de chacune vient de son aide argparse.
 COMMAND_GROUPS = (
     ("Projet", ("new", "adopt", "install", "update", "set", "waive")),
-    ("Au quotidien", ("dev", "check", "ci", "contrat", "doctor")),
+    ("Au quotidien", ("dev", "check", "ci", "contrat", "doctor", "completion")),
     ("Tous les repos", ("status", "update --all", "version")),
 )
 FLEET_UPDATE_ROLE = "mettre à jour chaque repo kiln, fusion directe"
@@ -106,9 +106,48 @@ def build_parser() -> argparse.ArgumentParser:
         "--poste", action="store_true", help="réglages du poste, même depuis un repo"
     )
     _add_waive_command(commands)
+    completion_parser = commands.add_parser(
+        "completion", help="script de complétion du shell (eval dans ~/.bashrc)"
+    )
+    completion_parser.add_argument("shell", choices=["bash"], help="shell visé")
     return parser
 
 
+def generate_bash_completion() -> str:
+    """Script de complétion bash tiré du parser : commandes, puis options et choix de chacune."""
+    subparsers = next(
+        action
+        for action in build_parser()._actions
+        if isinstance(action, argparse._SubParsersAction)
+    )
+    cases: list[str] = []
+    for name, subparser in sorted(subparsers.choices.items()):
+        words: set[str] = set()
+        for action in subparser._actions:
+            words.update(action.option_strings)
+            if not action.option_strings and action.choices:
+                words.update(str(choice) for choice in action.choices)
+        cases.append(
+            f"        {name})\n"
+            f'            COMPREPLY=( $(compgen -W "{" ".join(sorted(words))}" -- "$cur") )\n'
+            f"            ;;"
+        )
+    commands = " ".join(sorted(subparsers.choices))
+    return f"""# kiln bash completion: eval "$(kiln completion bash)"
+_kiln_completion() {{
+    local cur="${{COMP_WORDS[COMP_CWORD]}}"
+    COMPREPLY=()
+    if [[ $COMP_CWORD -eq 1 ]]; then
+        COMPREPLY=( $(compgen -W "{commands}" -- "$cur") )
+        return 0
+    fi
+    case "${{COMP_WORDS[1]}}" in
+{"\n".join(cases)}
+    esac
+}}
+complete -F _kiln_completion kiln"""
+
+
 def _add_waive_command(commands: argparse._SubParsersAction[argparse.ArgumentParser]) -> None:
     waive_parser = commands.add_parser(
         "waive", help="déroger à une règle de kiln, ou figer un fichier (sans argument : lister)"
@@ -231,6 +270,9 @@ BANNER_ACTIONS = {
 
 
 def dispatch(arguments: argparse.Namespace) -> None:
+    if arguments.command == "completion":
+        print(generate_bash_completion())
+        return
     _show_banner(arguments)
     if arguments.command == "new":
         new.create_project(_new_project_request(arguments))

{kiln_cli-0.3.2 → kiln_cli-0.3.3}/src/kiln/fleet.py

@@ -18,7 +18,7 @@ from kiln.check import run_checks
 from kiln.install import install_project
 from kiln.shell import KilnError, capture, require_tools, run, step
 from kiln.stack import ANSWERS_FILE, CHARTER_FILE, answers_if_any, load_stack, read_answers
-from kiln.update import update_project
+from kiln.update import conflicted_files, update_project
 from kiln.versions import latest_release, release_version
 
 KILN_SOURCE_MARKERS = ("antoine-tena/kiln", "antoine-tena/init-repo")
@@ -36,7 +36,6 @@ PREFERRED_INTEGRATION_BRANCH = "develop"
 MAX_FILES_PER_COMMIT = 10
 # pre-commit refuse de tourner tant que sa configuration modifiée n'est pas commitée.
 FIRST_COMMITTED = ".pre-commit-config.yaml"
-CONFLICT_MARKER = "<<<<<<< before updating"
 COMMIT_ATTEMPTS = 2
 
 
@@ -219,18 +218,6 @@ def _update_worktree(worktree: Path, *, allow_major: bool) -> list[str]:
     return run_checks(worktree)
 
 
-def conflicted_files(worktree: Path) -> list[str]:
-    """Fichiers où Copier a laissé un conflit à résoudre à la main."""
-    found = subprocess.run(
-        ["git", "grep", "-l", "--untracked", CONFLICT_MARKER],
-        cwd=worktree,
-        capture_output=True,
-        text=True,
-        check=False,
-    )
-    return found.stdout.split()
-
-
 def integration_branch(root: Path) -> str:
     preferred = subprocess.run(
         [