Adds proposals/274-skillfollow.md: an opt-in .skillfollow file that lets discovery follow declared first-level links in the skills source, so a tracked repo can live in the user projects directory. Without a .skillfollow, behavior does not change. The proposal answers the three requirements set in #274: a single source walker with a ratchet test, a three-part link ownership contract, and git staging and update rules for followed repos. Writes to the source go through an os.Root handle. Windows junction behavior was verified on a real machine.
Refs #274
Create Release Please PRs, synchronize release metadata, and test the exact merge commit before tagging and building an unpublished draft.
Verify release artifacts before manual publication and keep Homebrew and Docker distribution tied to the approved version. Document explicit version overrides and squash-merge behavior in the release skills and runbook.
Validation: make check, 12 release helper tests, actionlint, and an isolated six-platform GoReleaser build with artifact verification.
skillshare's git integration covers only the skills source today, so
extras (hooks, rules, commands, prompts) sit outside the commit/push/pull
workflow. This proposal asks that extras become a first-class git target.
Adds Status block documenting what actually shipped (sources map only,
no source shorthand) and resolves the two Open Questions (external
gitignore: leave to repo; init -p --source flag: deferred).
Restructure contribution guidelines to clarify expectations:
- Issues are the primary entry point for all contributions
- PRs are for small fixes; features require issue + proposal first
- Implementation is handled by maintainer after proposal approval
- All development must use devcontainer (make devc)
Add PR template to surface checklist when contributors open PRs.
Add proposals/ directory with TEMPLATE.md for feature proposals.