issue-216: Add the penpot skill and extension to the repo root README #250

Merged

david merged 2 commits from feature/issue-216/add-the-penpot-skill-and-extension-to-the-repo-roo into main

2026-09-15 08:50:13 +00:00

david commented

2026-09-15 08:50:12 +00:00

Owner

216: Add the penpot skill and extension to the repo root README

Closes #216 — 216.

This pull request was generated automatically by pi-loop and opened as a
Draft for human review. Do not merge without reviewing the changes.

Generated in 12m 19s.

Review findings

Both findings are Low-severity README text edits. Let me verify the facts first, then apply.Both facts verified. Applying the two Low-severity edits now.Now re-running the project's test gate to confirm nothing regressed:Both fixes applied and the test gate is green (864 tests: 863 pass, 0 fail, 1 skipped — unchanged from the Stage 2 baseline).

Review Findings — 216

Summary

Resolved both Low findings in a single pass: the penpot skill row now names the pinned Penpot 2.17.2 version and the vendored reference location instead of the vague "one version", and the prerequisites row now specifies that link/unlink tools additionally need edit rights on the library file itself (verified against extensions/penpot/README.md). npm test re-run after the edits: 863 pass / 0 fail / 1 skipped. No findings remain unresolved.

Critical

(none)

High

(none)

Medium

(none)

Low

README.md:22 — "Ships a vendored Penpot reference pinned to one version" is vague ("one version") and partly redundant with the table header sentence directly above ("penpot also ships a dependency-free fetch script and its vendored reference under skills/penpot/docs/"). Naming the version here would make the row self-contained, consistent with line 50 which pins 2.17.2. Suggested fix: change to "Ships a vendored Penpot reference pinned to Penpot 2.17.2 (skills/penpot/docs/)".
README.md:50 — "the token needs edit rights on a project to write" is accurate but slightly under-specified: per extensions/penpot/README.md (lines 39–40, 72), penpot_link_library/penpot_unlink_library additionally require edit permission on the library file (via Penpot's check-edition-permissions! on both ids), not only the consumer file's project. Suggested fix: append "(link/unlink also require edit rights on the library file itself)" or similar.

Notes

The issue title ("Add the penpot skill and extension to the repo root README") is largely satisfied by the penpot rows already present in both tables before this commit; this commit is the finishing polish (extension cross-reference, vendored-reference mention, edit-rights prerequisite). Both tables' counts (15 skills, 9 extensions) match the repository contents.
Commit message 216: Add the penpot skill and extension to the repo root README follows the repo's issue-<N>: <summary> convention.

## 216: Add the penpot skill and extension to the repo root README Closes #216 — [216](https://git.excelera.net/david/pi-extensions-and-skills/issues/216). > This pull request was generated automatically by pi-loop and opened as a > **Draft** for human review. Do not merge without reviewing the changes. Generated in 12m 19s. ## Review findings Both findings are Low-severity README text edits. Let me verify the facts first, then apply.Both facts verified. Applying the two Low-severity edits now.Now re-running the project's test gate to confirm nothing regressed:Both fixes applied and the test gate is green (864 tests: 863 pass, 0 fail, 1 skipped — unchanged from the Stage 2 baseline). # Review Findings — 216 ## Summary Resolved both Low findings in a single pass: the penpot skill row now names the pinned Penpot `2.17.2` version and the vendored reference location instead of the vague "one version", and the prerequisites row now specifies that link/unlink tools additionally need **edit** rights on the library file itself (verified against `extensions/penpot/README.md`). `npm test` re-run after the edits: 863 pass / 0 fail / 1 skipped. No findings remain unresolved. ## Critical - [ ] (none) ## High - [ ] (none) ## Medium - [ ] (none) ## Low - [x] README.md:22 — "Ships a vendored Penpot reference pinned to one version" is vague ("one version") and partly redundant with the table header sentence directly above ("`penpot` also ships a dependency-free fetch script and its vendored reference under `skills/penpot/docs/`"). Naming the version here would make the row self-contained, consistent with line 50 which pins `2.17.2`. Suggested fix: change to "Ships a vendored Penpot reference pinned to Penpot `2.17.2` (`skills/penpot/docs/`)". - [x] README.md:50 — "the token needs **edit** rights on a project to write" is accurate but slightly under-specified: per `extensions/penpot/README.md` (lines 39–40, 72), `penpot_link_library`/`penpot_unlink_library` additionally require **edit** permission on the *library file* (via Penpot's `check-edition-permissions!` on both ids), not only the consumer file's project. Suggested fix: append "(link/unlink also require edit rights on the library file itself)" or similar. ## Notes - The issue title ("Add the penpot skill and extension to the repo root README") is largely satisfied by the penpot rows already present in both tables before this commit; this commit is the finishing polish (extension cross-reference, vendored-reference mention, edit-rights prerequisite). Both tables' counts (15 skills, 9 extensions) match the repository contents. - Commit message `216: Add the penpot skill and extension to the repo root README` follows the repo's `issue-<N>: <summary>` convention.

david added 2 commits

2026-09-15 08:50:12 +00:00