eriktobben/hermes-backup/discord-channel-repo-routing

Claude Code and agent skill by eriktobben/hermes-backup

Trust tier 3
  • community
Source check pending

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-routing

SKILL.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

  1. One project per channel (or parent thread)
  2. One feature/fix per thread
  3. Explicit repo+branch header at thread start
  4. No cross-repo actions unless explicitly requested

Setup

Create a mapping file at:

~/.hermes/repo-map.yaml

Example format:

yaml
projects:
serena:
repo_path: ~/code/serena
default_branch: main
ig-flow:
repo_path: ~/code/ig-flow
default_branch: main
# Optional: exact Discord channel/thread IDs if you want strict routing docs
# discord:
# channel_id_to_project:
# "1498947405524107275": serena

Thread start template (paste in first message)

md
Repo: ~/code/<repo>
Branch: <feat/...|fix/...|chore/...>
Task: <short task description>
Constraints: <tests, style, deadlines>

Operating procedure

  1. Identify project from channel/thread name (e.g. serena, ig-flow).
  2. Resolve expected repo from ~/.hermes/repo-map.yaml.
  3. If thread header has a different repo, ask user which one to use before any file edits.
  4. Before coding, restate:
  • resolved repo path
  • target branch name
  • task scope
  1. 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.
  1. Perform all file/terminal actions only in that repo path unless user explicitly broadens scope.
  2. 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:

  1. Verify current repo path and branch are correct for this thread.
  2. Confirm if operation affects more than one repo.
  3. 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 main instead 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

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
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/eriktobben/hermes-backup/discord-channel-repo-routing/badge)](https://verified-skill.com/skills/eriktobben/hermes-backup/discord-channel-repo-routing)

Something wrong with this skill or its page? Tell us.