Mads LorentzenandClaude Opus 5 34b8b3f91f fix(onboarding): warn about public forks at the point of decision (#345) (#348) ...

The quick start walked a new user into gh repo fork - forks of public
repos are always public - and two steps later had /setup write personal
data into tracked files, with the only complete warning in SETUP.md
section 8, a section about pulling updates that a first-time user has no
reason to open during onboarding. A real user hit exactly this (#345).

The warning now sits adjacent to both fork commands (README step 1,
SETUP.md section 2, both pointing at section 8's private-remote recipe),
and /setup checks the origin's visibility BEFORE writing anything: a
public-fork origin gets a confirm-first warning instead of a note after
every file is on disk. A private origin, no origin, or a non-git
directory continues silently. Reported by @basilevs with a complete
reproduction and fix analysis; this implements his fixes (1) and (4).

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-19 21:33:32 +02:00

..

agents

Initial release: AI-powered job application framework

2026-03-23 08:34:06 +01:00

commands

fix(onboarding): warn about public forks at the point of decision (#345) (#348)

2026-08-19 21:33:32 +02:00

skills

fix(scrape): add a client-side recency fallback for flagless portals

2026-08-19 20:56:15 +02:00

settings.json

feat: add ATS & keyword verification pass to /apply's compile-and-inspect loop (#40)

2026-07-07 06:28:59 +02:00