From a9eaf7978e33a6832630c51f1bb87f97dbf5fe36 Mon Sep 17 00:00:00 2001 From: steelcityappliance Date: Sun, 6 Sep 2026 14:29:36 -0500 Subject: [PATCH] Point the shipped agent skills at omacom/omarchy (#10532) The repository moved from basecamp/omarchy to omacom/omarchy, but the skills Omarchy installs into ~/.claude/skills, ~/.codex/skills and ~/.agents/skills still name the old owner. Most gh calls follow the rename, so nothing looks wrong in normal use. Search does not: `gh issue list --repo basecamp/omarchy --search ...` exits 0 with no output, and the raw search API answers "Validation Failed". An agent following contributing.md or reporting.md runs its duplicate check before filing, sees zero matches, and files a duplicate. Replace the owner in contributing.md, reporting.md and the issue-template contact link, which is the same stale name on the contributor path. The git clone and release URLs in bin/ and manual/ are left alone: GitHub redirects those, and channel-test.sh asserts the exact clone URL, so changing them is a separate change. Fixes #10118 Written by Claude Fable 5.1 via Claude Code, reviewed by Marc Morriss Co-authored-by: Claude Fable 5.1 --- .github/ISSUE_TEMPLATE/config.yml | 2 +- default/agents/skills/diagnose-crash/reporting.md | 10 +++++----- default/agents/skills/omarchy/contributing.md | 8 ++++---- 3 files changed, 10 insertions(+), 10 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml index 2e9a3140..d353097d 100644 --- a/.github/ISSUE_TEMPLATE/config.yml +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -1,7 +1,7 @@ blank_issues_enabled: false contact_links: - name: Suggestion - url: https://github.com/basecamp/omarchy/discussions/categories/suggestions + url: https://github.com/omacom/omarchy/discussions/categories/suggestions about: Suggest a new feature, change to existing feature, or other ideas in Discussions. - name: Support url: https://omarchy.org/discord diff --git a/default/agents/skills/diagnose-crash/reporting.md b/default/agents/skills/diagnose-crash/reporting.md index 154f1a25..15bd08bc 100644 --- a/default/agents/skills/diagnose-crash/reporting.md +++ b/default/agents/skills/diagnose-crash/reporting.md @@ -40,8 +40,8 @@ useful; filing there yourself is not part of this. A duplicate issue costs a maintainer more time than no report at all. ```bash -gh search issues --repo basecamp/omarchy " crash" -gh issue list --repo basecamp/omarchy --state all --search " " +gh search issues --repo omacom/omarchy " crash" +gh issue list --repo omacom/omarchy --state all --search " " ``` Search on the crashing program, the signal, and distinctive symbols from the @@ -59,7 +59,7 @@ more than another duplicate. If a plausible match comes back, read it properly first: ```bash -gh issue view --repo basecamp/omarchy --comments +gh issue view --repo omacom/omarchy --comments ``` Confirm it is genuinely the same failure. The same program crashing is not the @@ -74,7 +74,7 @@ A comment that only says the bug happens to you too is noise. If that is all you have, tell the user so and file nothing. ```bash -gh issue comment --repo basecamp/omarchy --body "..." +gh issue comment --repo omacom/omarchy --body "..." ``` ## Filing a new issue @@ -82,7 +82,7 @@ gh issue comment --repo basecamp/omarchy --body "..." Only when the search turns up nothing that matches: ```bash -gh issue create --repo basecamp/omarchy --title "..." --body "..." +gh issue create --repo omacom/omarchy --title "..." --body "..." ``` Include what happened, what was expected, steps to reproduce, system details from diff --git a/default/agents/skills/omarchy/contributing.md b/default/agents/skills/omarchy/contributing.md index 117a9901..b5fd0533 100644 --- a/default/agents/skills/omarchy/contributing.md +++ b/default/agents/skills/omarchy/contributing.md @@ -3,13 +3,13 @@ Read this when the user wants to report an Omarchy bug, suggest a feature, or contribute a fix upstream. -Omarchy lives at https://github.com/basecamp/omarchy. Route requests to the +Omarchy lives at https://github.com/omacom/omarchy. Route requests to the right place: - **Verified bugs** -> GitHub issues. Issues are for validated bugs only, not support requests. - **Feature ideas and suggestions** -> - https://github.com/basecamp/omarchy/discussions/categories/suggestions + https://github.com/omacom/omarchy/discussions/categories/suggestions - **Support and "is this a bug?" questions** -> the Discord community at https://omarchy.org/discord. Start here when the problem isn't clearly a bug in Omarchy itself. @@ -43,7 +43,7 @@ For screen-recording failures specifically, rerun with File the issue with `gh` when available: ```bash -gh issue create --repo basecamp/omarchy --title "..." --body "..." +gh issue create --repo omacom/omarchy --title "..." --body "..." ``` Include: what happened, what was expected, steps to reproduce, system details, @@ -54,7 +54,7 @@ the debug log URL (or attached log), and the capture. Never develop against `/usr/share/omarchy`. Clone a working copy instead: ```bash -gh repo fork basecamp/omarchy --clone +gh repo fork omacom/omarchy --clone cd omarchy ```