create-sessions-dir 0.3.6 → 0.3.7

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-sessions-dir",
-  "version": "0.3.6",
+  "version": "0.3.7",
   "description": "Scaffold a Sessions Directory for working with AI coding agents",
   "type": "module",
   "bin": {

package/templates/claude/commands/archive-session.md

@@ -2,7 +2,11 @@
 description: Archive completed session work
 ---
 
-Review completed work in .sessions/ and archive it.
+**First**: Find the git root to locate session files (supports monorepos):
+- Run: `git rev-parse --show-toplevel` to get the repository root path
+- Session files live at `<git-root>/.sessions/`
 
-Move finished session notes to .sessions/archive/ organized by date or topic.
-Clean up .sessions/index.md by removing completed items.
+Review completed work in `<git-root>/.sessions/` and archive it.
+
+Move finished session notes to `<git-root>/.sessions/archive/` organized by date or topic.
+Clean up `<git-root>/.sessions/index.md` by removing completed items.

package/templates/claude/commands/document.md

@@ -2,12 +2,16 @@
 description: Create topic-specific documentation
 ---
 
-Create or update documentation for a specific topic in .sessions/docs/
+**First**: Find the git root to locate session files (supports monorepos):
+- Run: `git rev-parse --show-toplevel` to get the repository root path
+- Session files live at `<git-root>/.sessions/`
+
+Create or update documentation for a specific topic in `<git-root>/.sessions/docs/`
 
 The user will provide a topic name (e.g., "authentication", "api-design", "testing-strategy").
 
 Steps:
-1. If .sessions/docs/ doesn't exist, create it first
+1. If `<git-root>/.sessions/docs/` doesn't exist, create it first
 2. Ask: "What should be documented about [topic]?"
 3. Launch an Explore agent with:
    "Thoroughly explore the codebase to understand [topic].
@@ -20,13 +24,13 @@ Steps:
 
    Return a structured summary suitable for documentation."
 
-4. Use the agent's findings to create .sessions/docs/<topic>.md with:
+4. Use the agent's findings to create `<git-root>/.sessions/docs/<topic>.md` with:
    - Overview of the topic
    - Current decisions and rationale
    - Implementation details or patterns
    - Key files and code references (use file:line format)
    - Open questions or considerations
 
-5. Add reference to this doc in index.md under relevant section
+5. Add reference to this doc in `<git-root>/.sessions/index.md` under relevant section
 
 Keep documentation scannable with clear headings and bullet points.

package/templates/claude/commands/end-session.md

@@ -3,9 +3,13 @@ allowed-tools: Bash(git:*), Bash(.claude/scripts/*:*)
 description: End session and update context
 ---
 
+**First**: Find the git root to locate session files (supports monorepos):
+- Run: `git rev-parse --show-toplevel` to get the repository root path
+- Session files live at `<git-root>/.sessions/`
+
 ## Your task
 
-Update .sessions/index.md with session accomplishments.
+Update `<git-root>/.sessions/index.md` with session accomplishments.
 
 Include:
 - Today's date

package/templates/claude/commands/plan.md

@@ -2,10 +2,14 @@
 description: Create implementation plan
 ---
 
-Create or update a plan in .sessions/plans/
+**First**: Find the git root to locate session files (supports monorepos):
+- Run: `git rev-parse --show-toplevel` to get the repository root path
+- Session files live at `<git-root>/.sessions/`
+
+Create or update a plan in `<git-root>/.sessions/plans/`
 
 Steps:
-1. If .sessions/plans/ doesn't exist, create it first
+1. If `<git-root>/.sessions/plans/` doesn't exist, create it first
 2. Ask: "What are you planning to implement?"
 3. Launch a Plan agent with:
    "Help design the implementation for [description].
@@ -17,7 +21,7 @@ Steps:
    - Implementation steps
    - Risks and open questions"
 
-4. Create .sessions/plans/YYYY-MM-DD-<name>.md with structured plan:
+4. Create `<git-root>/.sessions/plans/YYYY-MM-DD-<name>.md` with structured plan:
 
 ```markdown
 # Plan: [Feature Name]
@@ -48,6 +52,6 @@ Steps:
 - Links to issues, PRs, other plans
 ```
 
-5. Add reference to plan in index.md: "Planning: [Feature] (see plans/YYYY-MM-DD-<name>.md)"
+5. Add reference to plan in `<git-root>/.sessions/index.md`: "Planning: [Feature] (see plans/YYYY-MM-DD-<name>.md)"
 
 Then ask: "Ready to start implementing?"

package/templates/claude/commands/start-session.md

@@ -1,11 +1,15 @@
 ---
-allowed-tools: Bash(gh:*), Bash(linearis:*)
+allowed-tools: Bash(gh:*), Bash(linearis:*), Bash(git rev-parse --show-toplevel)
 description: Start a new session
 ---
 
-Read .sessions/index.md and report when ready.
+**First**: Find the git root to locate session files (supports monorepos):
+- Run: `git rev-parse --show-toplevel` to get the repository root path
+- Session files live at `<git-root>/.sessions/`
 
-Check if .sessions/WORKSPACE.md exists (don't error if missing). If it exists, mention that monorepo support is active and show detected packages.
+Read `<git-root>/.sessions/index.md` and report when ready.
+
+Check if `<git-root>/.sessions/WORKSPACE.md` exists (don't error if missing). If it exists, mention that monorepo support is active and show detected packages.
 
 Summarize:
 - Current state
@@ -21,7 +25,7 @@ If user provides a GitHub/Linear URL or issue ID:
   - **GitHub**: gh issue view [URL] --json title,body,state,labels
   - **Linear**: linearis issues read [ID] (e.g., DEV-456, GTMENG-304)
   - Summarize the fetched context
-  - Store in .sessions/prep/YYYY-MM-DD-topic.md
+  - Store in `<git-root>/.sessions/prep/YYYY-MM-DD-topic.md`
   - Add reference to index.md
 
 Otherwise (continuing work, ad-hoc task, etc.):