Skip to content

SK-561: Add a dev-oriented post on git vault setup#168

Merged
mzgajner merged 3 commits into
mainfrom
mzgajner/sk-561-write-a-blog-post-on-setting-up-a-git-vault
Jun 18, 2026
Merged

SK-561: Add a dev-oriented post on git vault setup#168
mzgajner merged 3 commits into
mainfrom
mzgajner/sk-561-write-a-blog-post-on-setting-up-a-git-vault

Conversation

@mzgajner

Copy link
Copy Markdown
Contributor

This PR adds a blog post that attempts to be a bit shorter and more dev-oriented, focusing on how you set up a git vault with sx.

@mzgajner mzgajner requested review from detkin, inesp and mrdon as code owners June 17, 2026 14:51
@linear-code

linear-code Bot commented Jun 17, 2026

Copy link
Copy Markdown

SK-561

@claude

claude Bot commented Jun 17, 2026

Copy link
Copy Markdown

Claude finished @mzgajner's task in 1m 53s —— View job


A clean, technically accurate dev-oriented post — the CLI commands and scope flags all match the current sx codebase; only a few minor consistency/editorial nits.

[LOW] Filename slug doesn't match the post title

Location: site/_posts/2026-06-17-why-we-built-sx.md:3

Issue: The file is named ...-why-we-built-sx.md (so the published URL slug becomes why-we-built-sx), but the title is "Manage your org's skills from one place". The slug and title diverging makes the URL confusing and harder to find later. The sibling post (2026-06-05-a-package-manager-for-ai-assets.md) keeps slug and title aligned.

Suggestion: Rename the file to match the title, e.g. 2026-06-17-manage-your-orgs-skills-from-one-place.md, or pick a title that reflects "why we built sx".

[LOW] Missing `image` front matter (no social/OG preview)

Location: site/_posts/2026-06-17-why-we-built-sx.md:1-10

Issue: The existing post sets image: /sx/assets/sx-hero.png, which drives the social-share/OG card. This post has description but no image, so link previews on Slack/X/LinkedIn will render without an image and look inconsistent with the other post.

Suggestion: Add image: /sx/assets/sx-hero.png (or a post-specific hero) to the front matter for consistency.

[LOW] The gitignore advice may contradict the earlier "repo-specific skills are part of the repo" point

Location: site/_posts/2026-06-17-why-we-built-sx.md:73-84

Issue: Line 17 praises repo-specific skills being committed ("part of the repo … implicitly up to date"), but the gotcha section tells readers to delete and .gitignore the entire .claude/, .cursor/, .codex/ folders. A reader who currently hand-commits skills under .claude/skills/ could read this as "delete my committed skills" and lose hand-maintained, non-sx-managed assets.

Suggestion: Clarify that this applies to folders sx writes into / manages, and call out that anything you still commit by hand should be handled separately (or note that sx-managed assets should now live in the vault, not the repo).

[NIT] Unusual footnote label `[^x]`

Location: site/_posts/2026-06-17-why-we-built-sx.md:23,94

Issue: The footnote uses the identifier x. It renders fine in kramdown, but a non-numeric label is unconventional and slightly odd if more footnotes are added later.

Suggestion: Use a numbered/descriptive label like [^1] or [^standards].

I checked the technical accuracy against the codebase and everything in the post matches: sx init --type git --repo-url … (internal/commands/init.go:80-82), sx add … --repo … (repeatable, add.go:119), and the scope flags --org / --team / --repo / --path / --user are all current, non-deprecated flags. The pages.yml action version bumps are a safe, sensible maintenance change.

@mzgajner mzgajner force-pushed the mzgajner/sk-561-write-a-blog-post-on-setting-up-a-git-vault branch from 16096ed to 85bf8b1 Compare June 17, 2026 14:56
@claude

claude Bot commented Jun 17, 2026

Copy link
Copy Markdown

Claude finished @mzgajner's task in 56s —— View job


The renamed file now resolves the earlier slug mismatch, the CLI commands and scope flags all match the current sx codebase, and only the same few minor editorial nits remain.

[LOW] Missing `image` front matter (no social/OG preview)

Location: site/_posts/2026-06-17-all-your-skills-should-live-in-one-place.md:6-10

Issue: The sibling post sets image: /sx/assets/sx-hero.png, which drives the social-share/OG card. This post has description but no image, so link previews on Slack/X/LinkedIn will render without an image and look inconsistent with the other post.

Suggestion: Add image: /sx/assets/sx-hero.png (or a post-specific hero) to the front matter for consistency. Fix this →

[LOW] The gitignore advice may contradict the earlier "repo-specific skills are part of the repo" point

Location: site/_posts/2026-06-17-all-your-skills-should-live-in-one-place.md:73-84

Issue: Line 17 praises repo-specific skills being committed ("part of the repo … implicitly up to date"), but the gotcha section tells readers to delete and .gitignore the entire .claude/, .cursor/, .codex/ folders. A reader who currently hand-commits skills under .claude/skills/ could read this as "delete my committed skills" and lose hand-maintained, non-sx-managed assets.

Suggestion: Clarify that this applies to the folders sx writes into / manages, and note that anything you still commit by hand should be handled separately (or that sx-managed assets should now live in the vault rather than the repo).

[NIT] Unusual footnote label `[^x]`

Location: site/_posts/2026-06-17-all-your-skills-should-live-in-one-place.md:23,94

Issue: The footnote uses the identifier x. It renders fine in kramdown, but a non-numeric label is unconventional and slightly odd if more footnotes are added later.

Suggestion: Use a numbered/descriptive label like [^1] or [^standards].


Verified against the codebase: sx init --type git --repo-url … (internal/commands/init.go:82, --repo-url required for type=git at init.go:286), sx add … --repo … (repeatable StringArrayVar, add.go:119), and the scope flags --org / --team / --repo / --path / --user (add.go:118-122) are all current. The previous slug-mismatch finding is now resolved by the file rename. The pages.yml action version bumps are a safe maintenance change.

@mzgajner mzgajner force-pushed the mzgajner/sk-561-write-a-blog-post-on-setting-up-a-git-vault branch from 85bf8b1 to fecbc3c Compare June 17, 2026 15:03
@claude

claude Bot commented Jun 17, 2026

Copy link
Copy Markdown

Claude finished @mzgajner's task in 58s —— View job


A clean, dev-oriented post whose CLI commands and scope flags all match the current sx codebase; only a few minor editorial nits remain.

[LOW] Missing `image` front matter (no social/OG preview)

Location: site/_posts/2026-06-17-all-your-skills-should-live-in-one-place.md:6-10

Issue: The sibling post (2026-06-05-a-package-manager-for-ai-assets.md:9) sets image: /sx/assets/sx-hero.png, which drives the social-share/OG card. This post has description but no image, so link previews on Slack/X/LinkedIn will render without an image and look inconsistent with the other post.

Suggestion: Add image: /sx/assets/sx-hero.png (or a post-specific hero) to the front matter for consistency. Fix this →

[LOW] The gitignore gotcha may read as "delete my hand-committed skills"

Location: site/_posts/2026-06-17-all-your-skills-should-live-in-one-place.md:73-84

Issue: Line 17 praises repo-specific skills being committed ("part of the repo … implicitly up to date"), but the gotcha section tells readers to delete the entire .claude/, .cursor/, .codex/ folders and .gitignore them. A reader who currently hand-commits skills under .claude/skills/ (and isn't managing them via sx) could read this as "delete my committed skills" and lose hand-maintained assets.

Suggestion: Clarify that this applies to the folders sx writes into / manages, and note that anything you still commit by hand should either move into the vault or be handled separately.

[NIT] Unusual footnote label `[^x]`

Location: site/_posts/2026-06-17-all-your-skills-should-live-in-one-place.md:23,94

Issue: The footnote uses the identifier x. It renders fine in kramdown, but a non-numeric label is unconventional and slightly odd if more footnotes are added later.

Suggestion: Use a numbered or descriptive label like [^1] or [^standards].


Verified against the codebase: sx init --type git --repo-url … (internal/commands/init.go), sx add … --repo … (repeatable StringArrayVar, add.go:119), and the scope flags --org (add.go:118), --team (:121), --repo (:119), --path (:120), --user (:122) are all current, non-deprecated flags. The pages.yml action version bumps (checkout v6, configure-pages v6, upload-pages-artifact v5, deploy-pages v5) are a safe maintenance change.
mzgajner/sk-561-write-a-blog-post-on-setting-up-a-git-vault

@claude

claude Bot commented Jun 18, 2026

Copy link
Copy Markdown

Claude finished @mzgajner's task in 54s —— View job


A clean, dev-oriented post whose CLI commands and scope flags all match the current sx codebase; only a few minor editorial nits remain.

[LOW] Missing `image` front matter (no social/OG preview)

Location: site/_posts/2026-06-17-put-all-your-skills-in-one-place.md:6-10

Issue: The sibling post (2026-06-05-a-package-manager-for-ai-assets.md:10) sets image: /sx/assets/sx-hero.png, which drives the social-share/OG card. This post has description but no image, so link previews on Slack/X/LinkedIn will render without an image and look inconsistent with the other post.

Suggestion: Add image: /sx/assets/sx-hero.png (or a post-specific hero) to the front matter for consistency. Fix this →

[LOW] The gitignore gotcha may read as "delete my hand-committed skills"

Location: site/_posts/2026-06-17-put-all-your-skills-in-one-place.md:71-73

Issue: Line 17 praises repo-specific skills being committed ("part of the repo … implicitly up to date"), but the gotcha section tells readers to delete the entire .claude/, .cursor/, .codex/ folders and .gitignore them. A reader who currently hand-commits skills under .claude/skills/ (and isn't yet managing them via sx) could read this as "delete my committed skills" and lose hand-maintained assets.

Suggestion: Clarify that this applies to the folders sx writes into / manages, and note that anything you still commit by hand should either move into the vault or be handled separately.

[NIT] Unusual footnote label `[^x]`

Location: site/_posts/2026-06-17-put-all-your-skills-in-one-place.md:23,83

Issue: The footnote uses the identifier x. It renders fine in kramdown, but a non-numeric label is unconventional and slightly odd if more footnotes are added later.

Suggestion: Use a numbered or descriptive label like [^1] or [^standards].


Verified against the codebase: sx init --type git --repo-url … (internal/commands/init.go:68), sx install (internal/commands/install.go:57), sx add … --repo … (repeatable StringArrayVar, add.go:119), and the scope flags --org (add.go:118), --repo (:119), --path (:120), --team (:121), --user (:122) are all current, non-deprecated flags (the --scope* variants are the deprecated ones, correctly avoided here). The pages.yml action version bumps are a safe maintenance change.
mzgajner/sk-561-write-a-blog-post-on-setting-up-a-git-vault

@mzgajner mzgajner merged commit cd1a162 into main Jun 18, 2026
4 checks passed
@mzgajner mzgajner deleted the mzgajner/sk-561-write-a-blog-post-on-setting-up-a-git-vault branch June 18, 2026 09:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant