cs-repo

# CS Ops — AI Assistant for the Slabstack CS Team You type a command. Claude reads your real data, writes the output, and shows it to you before doing anything. Nothing gets posted or sent without your OK. Works on **Mac, Linux, and Windows** (Windows via WSL2 for full sandbox protection; native Windows works for everything except the OS-level Bash sandbox). Setup docs have side-by-side **Mac:** / **PC:** instructions. --- **Joining as a teammate (fork → clone → configure)?** → [TEAM_SETUP.md](TEAM_SETUP.md) — full handoff path, ~20 min **Already cloned, need to configure your machine?** → [SETUP.md](SETUP.md) — per-person config, ~10 min **Already set up, want to know what commands exist?** → [USER_GUIDE.md](USER_GUIDE.md) — every command explained, plus Claude Code 101 and GitHub 101 sections for newcomers --- ## What it does **Standup updates** — pulls your emails, calendar, Asana, and Intercom, then writes your standup in the team format. You review it and decide whether to post. **Intercom reports** — conversation counts, response times, and customer breakdowns in a Word doc. Five time ranges: daily through year-to-date. **Onboarding reports** — reads the Finance Pending Transactions sheet, cross-checks with Asana, and shows which accounts are on track, at risk, or done. **Renewal invoice reports** — reads the Finance renewals sheet and calculates exactly what each customer owes. Handles volume and fixed-rate contracts automatically. **Portfolio intelligence** — `/health-score` for a green/yellow/red view of every active account, `/at-risk` to surface risk signals across all systems, `/expansion` to find upsell opportunities, `/renewal-health` for upcoming renewal pipeline with risk scores. **Lifecycle commands** — `/start-onboarding` to kick off a new customer (Asana + Drive + Shortcut + Slack), `/end-onboarding` to close it out cleanly, `/handoff` to transfer account ownership with a full context brief. **Executive reporting** — `/executive-summary` for a portfolio-wide view combining onboarding, support, renewals, and health, `/weekly-team` to roll up the team's week for leadership. **Utilities** — `/customer` for a pre-call briefing, `/customer-search` for fuzzy customer lookup across all systems, `/inbox-triage` to sort the morning email pile, `/meeting-notes` for a structured post-meeting summary (read-only, no email), `/standup-recap` to roll up the week's daily files for `/eow`, `/escalate` to create a Shortcut ticket, `/my-tasks` to manage Asana, `/kb-draft` to write a KB article. **Discoverability** — `/commands` lists every available slash command pulled live from `.claude/commands/*.md` frontmatter (and flags any drift between the directory and CLAUDE.md). --- ## How it works Open a terminal, go to the `cs-repo` folder, and type `claude`. Then type any command. Claude does the work, shows you what it made, and asks before taking any action. Connects to: **Gmail, Google Calendar, Google Drive, Asana, Intercom, Slack, and Shortcut** — all through your own work accounts. Reports save as Word docs in `out/` (and auto-copy to your Desktop if you ran the Desktop setup). --- ## Changing files in this repo All edits go through a branch → PR → merge flow. Direct commits to `main` are blocked automatically. 1. Tell Claude what to change — it creates a branch, makes the edit, and pushes it 2. Claude opens a PR for your review 3. You merge on GitHub (squash and merge) Full walkthrough (no tech experience needed) → [USER_GUIDE.md § GitHub tutorial](USER_GUIDE.md#github-tutorial-no-tech-experience-needed) --- ## Repo quality Every hook, lib helper, chart, and report is covered by automated tests. Two linters (ruff for Python, biome for JS), mypy type-checking, and c8 coverage tracking on the JS side catch issues before they reach CI. GitHub Actions runs the full suite on every pull request so broken changes can't land on `main`. ``` source .venv/bin/activate # one-time per shell (or set up direnv — see CONTRIBUTING.md) make test # 869 tests (712 Python + 157 JS) make typecheck # mypy — Python type checking (lenient baseline) make test-cov # pytest with coverage threshold (≥85%) make test-js-cov # JS tests under c8 with coverage threshold (≥75%) make lint # ruff + biome — undefined names, unused imports, etc. /review-code # structured checklist — runs tests first, then 23 fixed sections ``` See [USER_GUIDE.md § Testing and quality](USER_GUIDE.md#testing-and-quality) for details. --- ## Reporting a security issue Found a vulnerability or a leaked token? See **[SECURITY.md](SECURITY.md)** for the reporting process, what's in scope, and the existing defense layers (`secret-scan`, `push-guard`, `file-protector`, `draft-before-create`, Bash sandbox with credential-dir deny-read, per-command tool restrictions, manual-only commands, branch protection, etc.). --- ## Intercom ID reference Each teammate needs their own ID so Claude pulls your conversations, not a teammate's. See Step 3 in [SETUP.md](SETUP.md) for how to find yours — `/setup` writes it into your local `CLAUDE.md`.