Skip to content

paultyng/skill-issue / skills/set-session-context

set-session-context

Verified

Use when starting a session on a non-main branch, switching branches (git checkout, git switch), or when a hook prompts for session context update. Also invocable manually via /set-session-context.

FileKindSize
SKILL.mdskill md1.5 KB
---
name: set-session-context
description: >-
  Use when starting a session on a non-main branch, switching branches
  (git checkout, git switch), or when a hook prompts for session context
  update. Also invocable manually via /set-session-context.
---

# Set Session Context

Automatically set session name and color based on the current git branch and PR.

## Steps

1. **Detect branch:**
   ```bash
   git symbolic-ref --short HEAD
   ```
   - If detached HEAD (command fails) → stop, do nothing
   - If `main` or `master` → stop, do nothing

2. **Look up PR title:**
   ```bash
   gh pr view --json title --jq '.title'
   ```

3. **Determine session name:**
   - If PR exists → use PR title
   - If no PR → humanize branch name: strip the conventional prefix and slash/hyphen separator, replace remaining hyphens with spaces
     - `feat/add-widget` → `add widget`
     - `fix-login-bug` → `login bug`

4. **Run:** `/rename <session name>`

5. **Determine color** from the branch prefix (match `^(type)[/-]`):

   | Prefix | Color |
   |---|---|
   | `feat` | blue |
   | `fix` | red |
   | `chore` | green |
   | `docs` | cyan |
   | `refactor` | yellow |
   | `test` | purple |
   | `ci` | orange |
   | `build` | orange |
   | `perf` | yellow |
   | `style` | cyan |
   | _(no match)_ | blue |

6. **Run:** `/color <color>`

## Behavior

- Execute silently: do not announce, explain, or narrate what you are doing.
- Do not ask for confirmation.
- If `gh` is unavailable or fails, fall back to the humanized branch name.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall