@corners/cli 0.0.5 → 0.0.7

package/skills/corners-sync/SKILL.md

@@ -0,0 +1,245 @@
+---
+name: corners-sync
+version: 0.1.0
+description: |
+  Pull workstream context and present a structured briefing.
+  Shows recent activity, open questions, and suggested next actions.
+  Offers to answer open questions inline and writes context to memory.
+allowed-tools:
+  - Bash
+  - Read
+  - Write
+  - AskUserQuestion
+---
+
+# /corners-sync — "Get me up to speed"
+
+Pull context from your connected workstream, present a structured briefing,
+answer open questions inline, and write key context to memory for future sessions.
+
+---
+
+## Step 0: Preamble
+
+Run these commands to check auth and resolve context:
+
+```bash
+corners auth status --json 2>/dev/null || echo "CORNERS_CLI_MISSING"
+```
+
+```bash
+corners workstream current --json 2>/dev/null
+```
+
+```bash
+_BRANCH=$(git branch --show-current 2>/dev/null || echo "unknown")
+echo "BRANCH: $_BRANCH"
+git log --oneline -5 2>/dev/null
+git status --short 2>/dev/null | head -10
+```
+
+**Error handling — check in this order:**
+
+1. If the first command printed `CORNERS_CLI_MISSING` or `command not found`: tell the user
+   "Corners CLI is not installed. Run `npm install -g @corners/cli` to install it." and **STOP**.
+
+2. Parse the auth status JSON. If `loggedIn` is `false` OR `remoteValid` is `false`:
+   tell the user "Your Corners session has expired. Run `corners auth login` to re-authenticate." and **STOP**.
+
+3. Parse the workstream current JSON. If `resolvedCorner` is null or missing:
+   tell the user "No corner is configured for this directory. Run `corners corner use <cornerId>` to set one up." and **STOP**.
+
+4. Check `connectedWorkstreamIds` in the workstream current JSON.
+   If the array is empty, proceed to Step 1 (workstream resolution).
+   If it has entries, skip to Step 2 using the first connected workstream ID.
+
+---
+
+## Step 1: Workstream Resolution (only if no workstream connected)
+
+Run:
+```bash
+corners workstream list --json 2>/dev/null
+```
+
+Parse the response. There are three scenarios:
+
+**Scenario A — Workstreams exist:**
+Normalize the current git branch name: strip common prefixes (`feat/`, `fix/`, `chore/`, `refactor/`),
+replace hyphens and underscores with spaces, and title-case the result.
+Compare this normalized name against the `name` field of each workstream in the list.
+
+If a workstream name is similar to the normalized branch name, use AskUserQuestion:
+- Question: "Found workstream '{name}' which seems related to your branch '{branch}'. Connect it?"
+- Options: "Yes, connect it" / "No, show me all workstreams" / "Create a new one instead"
+
+If "Yes": run `corners workstream use <id> --json` and proceed to Step 2.
+If "Show all": present the full list via AskUserQuestion and let the user pick.
+If "Create new": proceed to Scenario C.
+
+If no workstream name matches the branch, present the full list via AskUserQuestion
+and let the user pick one, or offer to create a new one.
+
+**Scenario B — No workstreams exist anywhere:**
+Use AskUserQuestion:
+- Question: "No workstreams exist yet. Create one to start tracking your work?"
+- Derive a suggested name from the current branch (e.g., `feat/auth-refactor` → "Auth Refactor")
+- Options: "Yes, create '{suggested name}'" / "Yes, with a different name" / "Skip — just show git context"
+
+If creating: run `corners workstream create "{name}" --json`, then `corners workstream use <returned id> --json`.
+
+**Scenario C — Create new:**
+Derive name from branch, confirm with user, run create + use.
+
+After resolution, proceed to Step 2 with the workstream ID.
+
+---
+
+## Step 2: Pull Workstream Context
+
+Run these commands to gather full context:
+
+```bash
+corners workstream pull <workstreamId> --json 2>/dev/null
+```
+
+```bash
+corners workstream question list <workstreamId> --json 2>/dev/null
+```
+
+Parse the JSON responses. Extract:
+- From pull: `workstream.id`, `workstream.name`, `workstream.summary`, `workstream.status`,
+  `threads[]`, `feedEvents[]`, `attachments[]`
+- From question list: `questions[]` with fields `id`, `questionText`, `rationale`,
+  `suggestedAnswers[]`, `askedBy`, `status`, `createdAt`
+
+If `feedEvents` or `threads` has more than 10 items, use only the most recent 10
+and note the total count.
+
+---
+
+## Step 3: Present Structured Briefing
+
+Display the briefing in this format:
+
+```
+## Workstream: {name} ({id})
+Status: {status}
+Summary: {summary}
+
+### Recent Activity
+{Summarize the last 10 feed events in 1-2 lines each. Include type, timestamp, and key content.}
+
+### Open Questions ({count})
+{For each open question:}
+- **{askedBy}** ({timeAgo}): "{questionText}"
+  Suggested answers: {list suggestedAnswers}
+
+### Threads ({count})
+{For each thread, show topic/subject and message count}
+
+### Attachments ({count})
+{List any linked documents, files, or artifacts}
+
+### Local Git State
+Branch: {branch}
+Recent commits: {list from git log}
+Working tree: {clean / N files modified}
+
+### Suggested Next Actions
+{Based on the context, suggest 2-3 concrete next steps. Examples:}
+- Answer Alice's question about the API schema
+- Review the latest thread about deployment
+- Continue work on the auth-refactor branch
+```
+
+---
+
+## Step 4: Answer-at-Sync
+
+After presenting the briefing, check if any open questions exist.
+
+For each open question (up to 3), use AskUserQuestion:
+- Re-ground: "Workstream '{name}' on branch {branch}."
+- Question: "{askedBy} asked: '{questionText}'"
+- If suggested answers exist, include them as options plus "Skip" and "Custom answer"
+- If no suggested answers, options: "Answer now" / "Skip"
+
+If the user provides an answer, post it:
+```bash
+corners workstream question answer <questionId> --text "$(cat <<'CORNERS_MSG'
+<user's answer text>
+CORNERS_MSG
+)" --json
+```
+
+If the user skips, move to the next question or proceed to Step 5.
+
+---
+
+## Step 5: Memory Write
+
+Write workstream context to Claude Code's memory system so it persists across conversations.
+
+Determine the memory directory path. It follows the pattern:
+`~/.claude/projects/-{path-with-hyphens}/memory/`
+
+For this project, the path is derived from the working directory. Use the memory
+directory that already exists for this project.
+
+Write a memory file named `workstream_{normalized_name}.md` (lowercase, hyphens for spaces):
+
+```markdown
+---
+name: Workstream context - {name}
+description: Active workstream {name} ({id}) - {summary}
+type: project
+---
+
+Connected workstream for this repository.
+
+- **ID:** {id}
+- **Name:** {name}
+- **Status:** {status}
+- **Summary:** {summary}
+
+**Open questions ({count}):**
+{For each: "- {askedBy}: {questionText}" — keep to 1 line each}
+
+**Recent activity:**
+{2-3 sentence summary of what's been happening}
+
+**How to apply:** When working in this repo, this workstream provides the coordination context. Check for open questions before starting new work. Use /corners-push to record progress.
+```
+
+Then read the existing `MEMORY.md` file in the same directory. If a reference to this
+workstream memory file doesn't already exist, add it under the `## Project` section.
+
+---
+
+## Manual Equivalent
+
+The raw CLI commands this skill orchestrates:
+
+```bash
+# Check auth
+corners auth status --json
+
+# Resolve local context
+corners workstream current --json
+
+# List available workstreams
+corners workstream list --json
+
+# Connect a workstream
+corners workstream use <wsId>
+
+# Pull full context
+corners workstream pull <wsId> --json
+
+# List open questions
+corners workstream question list <wsId> --json
+
+# Answer a question
+corners workstream question answer <questionId> --text "..." --json
+```