Repository navigation
0.1.29: every ck page names its project - #68
Merged
Merged
Conversation
A d20mob staged plan was published as "Phase 9, the ten: staged plan" under the banner line "Code Katz · review page", so nothing on the page said d20mob and Will could not tell it apart in his artifact list. render-review.py now finds the project's name itself: the main checkout's folder of the git repository that holds --in (from --git-common-dir, so a worktree still names the project), or the file's folder outside a repository. The name leads the banner line and the title, unless the title already starts with it. --project overrides it. Callers need no change. A git grep across skills/, workflows/ and scripts/ found two other ways a page is published: render-gallery.py (brand and design galleries and chosen.html), which now names the project the same way, and the /ck:do mockup, whose rules now ask for the project's name in its title and in one line above the mockup. scripts/project_name.py holds the lookup. One test renders from a temporary repository named demo, then with --project x. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Author
|
ck cost for this pull request: $1.87, built by 0.1.29: every ck page names its project. 0.1.29: every ck page names its project cost summary
Prices from https://platform.claude.com/docs/en/about-claude/pricing.md, as of 2026-11-06. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A d20mob staged plan was published as https://claude.ai/artifact/4g7KdMYiykorn35HJjmVR1, titled "Phase 9, the ten: staged plan" under the banner line "Code Katz · review page". Nothing on the page said d20mob, so it could not be told apart in the artifact list. The review page skill asked callers for
--title "<product>: <document>", but nothing enforced it, and /ck:plan passed a title with no product.What changes
scripts/render-review.pyfinds the project's name itself and shows it in the banner line ("d20mob · review page") and at the front of the<title>and heading ("d20mob: Phase 9, the ten: staged plan"). It skips the prefix when the title already starts with the name, so /ck:claude-md's ": How we work" is unchanged. The name is the main checkout's folder of the git repository that holds--in(git rev-parse --path-format=absolute --git-common-dir, then its parent), so a page built in a worktree still says d20mob; outside a repository it is the file's folder.--projectoverrides it. No caller changes.git grepacrossskills/,workflows/andscripts/found two other ways ck publishes a page:scripts/render-gallery.py, for brand galleries, design galleries andchosen.html, had "Code Katz · gallery review" and "Code Katz · chosen design". It now names the project the same way, from the repository that holds the variants JSON, with the same--projectflag. The gallery contract says so.workflows/brand.jsandworkflows/design-round.jscall it and need no change.<title><project>: <what you drew>and one line above the mockup,<project> · mockup, with the session filling in the name.scripts/project_name.pyholds the lookup both renderers use.Tests
tests/run.sh: 505 passed, 0 failed. One new test renders a page from a file in a temporary repository nameddemoand findsdemoin its title and banner, thenxwith--project x.demosays demo; the gallery fixture rendered here says ck.🤖 Generated with Claude Code