eriktobben/hermes-backup/discord-channel-repo-routing
Claude Code and agent skill by eriktobben/hermes-backup
- community
Checking that the SKILL.md file is still in the repository.
Map Discord channels/threads to git repositories and enforce per-task session hygiene for Hermes coding workflows.
Install
npx vskill@latest install eriktobben/hermes-backup/discord-channel-repo-routingSKILL.md
The same SKILL.md was published earlier as eriktobben/hermes-backup/discord-channel-repo-routing.
Discord Channel → Repo Routing
Use this skill when working in Discord with multiple software projects and repositories.
Goal
Ensure each project channel (and each feature/fix thread under it) stays pinned to the correct local git repo and branch context.
What this skill standardizes
- One project per channel (or parent thread)
- One feature/fix per thread
- Explicit repo+branch header at thread start
- No cross-repo actions unless explicitly requested
Setup
Create a mapping file at:
~/.hermes/repo-map.yaml
Example format:
Thread start template (paste in first message)
Operating procedure
- Identify project from channel/thread name (e.g.
serena,ig-flow). - Resolve expected repo from
~/.hermes/repo-map.yaml. - If thread header has a different repo, ask user which one to use before any file edits.
- Before coding, restate:
- resolved repo path
- target branch name
- task scope
- Verify the repo path exists on disk before running any git/file commands.
- If a provided path fails (common
~/...vs/home/<user>/...mismatch), quickly locate the repo under likely roots (e.g.~/Projects) and confirm/use the real absolute path. - Update the channel mapping note once the canonical path is confirmed.
- Perform all file/terminal actions only in that repo path unless user explicitly broadens scope.
- At completion, summarize changed files, tests run, and next git commands.
Naming conventions
- Thread names:
feat/<slug>,fix/<slug>,chore/<slug> - Branch names: same as thread name
- Session title: same as thread name
Safety checks
Before destructive git or filesystem operations:
- Verify current repo path and branch are correct for this thread.
- Confirm if operation affects more than one repo.
- If uncertain, stop and ask user.
Verification checklist
- [ ] Repo path matches project mapping
- [ ] Branch matches feature/fix intent
- [ ] No files changed outside mapped repo
- [ ] Tests/lint executed (or explicitly skipped)
Pitfalls
- Working from wrong cwd when switching projects quickly
- Reusing context from a different feature thread
- Running commits on
maininstead of feature branch
Mitigation: always include the thread start header and re-state repo/branch before edits.
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/.archive/autonomous-ai-agents/discord-channel-repo-routing/SKILL.md
Popularity
- 7-day trend score
- 5
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/eriktobben/hermes-backup/discord-channel-repo-routing)