Description
pkg/cli/shell_completion.go:209 and :281 return invalid bashrc path: %s / invalid zshrc path: %s with no reason the path was rejected or how to fix it — verified live at both lines on main (commit f2e8122). This is a specific instance of the same error-message style-guide gap (.github/skills/error-messages/SKILL.md) as the repo-slug validation issue, but a distinct file/area.
Fix
State what's wrong (e.g. path does not exist / isn't accessible), what's expected, and a suggested fix, e.g.:
fmt.Errorf("bashrc path %q does not exist or is not accessible — verify the path or set $HOME to a valid directory", bashrcPath)Adjust validation logic only if needed to report an accurate reason (e.g. distinguish "does not exist" vs "not a file"); otherwise behavior stays the same. Update existing shell-completion tests. Run make fmt.
Expected Impact
Clearer diagnosis when shell-completion install fails for a bad rc-file path.
Suggested Agent
Copilot coding agent.
Estimated Effort
Quick (< 1 hour)
Data Source
DeepReport Intelligence Briefing 2026-08-21, mining discussion #54543, Task 3.
Generated by 🔬 Deep Report · agent · 106.7 AIC · ⌖ 8.62 AIC · ⊞ 12.4K · ◷
Description
pkg/cli/shell_completion.go:209and:281returninvalid bashrc path: %s/invalid zshrc path: %swith no reason the path was rejected or how to fix it — verified live at both lines onmain(commit f2e8122). This is a specific instance of the same error-message style-guide gap (.github/skills/error-messages/SKILL.md) as the repo-slug validation issue, but a distinct file/area.Fix
State what's wrong (e.g. path does not exist / isn't accessible), what's expected, and a suggested fix, e.g.:
Adjust validation logic only if needed to report an accurate reason (e.g. distinguish "does not exist" vs "not a file"); otherwise behavior stays the same. Update existing shell-completion tests. Run
make fmt.Expected Impact
Clearer diagnosis when shell-completion install fails for a bad rc-file path.
Suggested Agent
Copilot coding agent.
Estimated Effort
Quick (< 1 hour)
Data Source
DeepReport Intelligence Briefing 2026-08-21, mining discussion #54543, Task 3.