Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
Skill docs point at stale basecamp/omarchy repo path (now omacom/omarchy)
Reported by rkondratowicz · filed Sep 21, 2026Closed upstream on 2026-09-21 by its own reporter rkondratowicz. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- Not yet mapped to any requirement or component.
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
What happened
The agent skill docs shipped under /usr/share/omarchy/default/agents/skills/ still point at the old repository path basecamp/omarchy. The repo has moved and now redirects to omacom/omarchy (verified: gh repo view basecamp/omarchy reports nameWithOwner: omacom/omarchy).
Stale references:
omarchy/contributing.md
- Line 6: https://github.com/basecamp/omarchy
- Line 12: https://github.com/basecamp/omarchy/discussions/categories/suggestions
- Line 46: gh issue create --repo basecamp/omarchy ...
- Line 57: gh repo fork basecamp/omarchy --clone
diagnose-crash/reporting.md
- Line 43: gh search issues --repo basecamp/omarchy ...
- Line 44: gh issue list --repo basecamp/omarchy ...
- Line 62: gh issue view <number> --repo basecamp/omarchy ...
- Lines 77, 85: gh issue comment/create --repo basecamp/omarchy ...
Why it matters
gh follows the redirect, so commands still work, but an agent following these docs reports the wrong canonical repo to users and links the old URL. Anyone filing or searching issues is pointed at a path that is no longer authoritative.
What was expected
The docs should reference the canonical omacom/omarchy path (or the redirect documenting itself in an obvious way).
Steps to reproduce
rg -n "basecamp/omarchy" /usr/share/omarchy/default/agents/skills/
gh repo view basecamp/omarchy --json nameWithOwnerThe first prints the stale references; the second confirms the redirect target is omacom/omarchy.
Suggested fix
Update all references in the two skill files from basecamp/omarchy to omacom/omarchy.
System details
- Omarchy: 4.0.4-1 (stable channel)
- Kernel: 7.2.5-3-omarchy
View raw text
## What happened The agent skill docs shipped under `/usr/share/omarchy/default/agents/skills/` still point at the old repository path `basecamp/omarchy`. The repo has moved and now redirects to `omacom/omarchy` (verified: `gh repo view basecamp/omarchy` reports `nameWithOwner: omacom/omarchy`). Stale references: `omarchy/contributing.md` - Line 6: `https://github.com/basecamp/omarchy` - Line 12: `https://github.com/basecamp/omarchy/discussions/categories/suggestions` - Line 46: `gh issue create --repo basecamp/omarchy ...` - Line 57: `gh repo fork basecamp/omarchy --clone` `diagnose-crash/reporting.md` - Line 43: `gh search issues --repo basecamp/omarchy ...` - Line 44: `gh issue list --repo basecamp/omarchy ...` - Line 62: `gh issue view <number> --repo basecamp/omarchy ...` - Lines 77, 85: `gh issue comment/create --repo basecamp/omarchy ...` ## Why it matters `gh` follows the redirect, so commands still work, but an agent following these docs reports the wrong canonical repo to users and links the old URL. Anyone filing or searching issues is pointed at a path that is no longer authoritative. ## What was expected The docs should reference the canonical `omacom/omarchy` path (or the redirect documenting itself in an obvious way). ## Steps to reproduce ```bash rg -n "basecamp/omarchy" /usr/share/omarchy/default/agents/skills/ gh repo view basecamp/omarchy --json nameWithOwner ``` The first prints the stale references; the second confirms the redirect target is `omacom/omarchy`. ## Suggested fix Update all references in the two skill files from `basecamp/omarchy` to `omacom/omarchy`. ## System details - Omarchy: 4.0.4-1 (stable channel) - Kernel: 7.2.5-3-omarchy
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
No decision has been recorded yet.