From d687db5eec673de25f82ae42a6d1516f4b0ad1e8 Mon Sep 17 00:00:00 2001 From: Garry Tan Date: Sun, 22 Mar 2026 13:17:05 -0700 Subject: [PATCH] chore: regenerate SKILL.md files after main merge --- .agents/skills/gstack-autoplan/SKILL.md | 15 +++++++++++++++ .agents/skills/gstack-retro/SKILL.md | 22 ++++++++++++++++++++++ autoplan/SKILL.md | 15 +++++++++++++++ 3 files changed, 52 insertions(+) diff --git a/.agents/skills/gstack-autoplan/SKILL.md b/.agents/skills/gstack-autoplan/SKILL.md index 6c2535e7..89eeb1c2 100644 --- a/.agents/skills/gstack-autoplan/SKILL.md +++ b/.agents/skills/gstack-autoplan/SKILL.md @@ -27,6 +27,9 @@ _PROACTIVE=$(~/.codex/skills/gstack/bin/gstack-config get proactive 2>/dev/null _BRANCH=$(git branch --show-current 2>/dev/null || echo "unknown") echo "BRANCH: $_BRANCH" echo "PROACTIVE: $_PROACTIVE" +source <(~/.codex/skills/gstack/bin/gstack-repo-mode 2>/dev/null) || true +REPO_MODE=${REPO_MODE:-unknown} +echo "REPO_MODE: $REPO_MODE" _LAKE_SEEN=$([ -f ~/.gstack/.completeness-intro-seen ] && echo "yes" || echo "no") echo "LAKE_INTRO: $_LAKE_SEEN" _TEL=$(~/.codex/skills/gstack/bin/gstack-config get telemetry 2>/dev/null || true) @@ -127,6 +130,18 @@ AI-assisted coding makes the marginal cost of completeness near-zero. When you p - BAD: "Let's defer test coverage to a follow-up PR." (Tests are the cheapest lake to boil.) - BAD: Quoting only human-team effort: "This would take 2 weeks." (Say: "2 weeks human / ~1 hour CC.") +## Repo Ownership Mode — See Something, Say Something + +`REPO_MODE` from the preamble tells you who owns issues in this repo: + +- **`solo`** — One person does 80%+ of the work. They own everything. When you notice issues outside the current branch's changes (test failures, deprecation warnings, security advisories, linting errors, dead code, env problems), **investigate and offer to fix proactively**. The solo dev is the only person who will fix it. Default to action. +- **`collaborative`** — Multiple active contributors. When you notice issues outside the branch's changes, **flag them via AskUserQuestion** — it may be someone else's responsibility. Default to asking, not fixing. +- **`unknown`** — Treat as collaborative (safer default — ask before fixing). + +**See Something, Say Something:** Whenever you notice something that looks wrong during ANY workflow step — not just test failures — flag it briefly. One sentence: what you noticed and its impact. In solo mode, follow up with "Want me to fix it?" In collaborative mode, just flag it and move on. + +Never let a noticed issue silently pass. The whole point is proactive communication. + ## Search Before Building Before building infrastructure, unfamiliar patterns, or anything the runtime might have a built-in — **search first.** Read `~/.codex/skills/gstack/ETHOS.md` for the full philosophy. diff --git a/.agents/skills/gstack-retro/SKILL.md b/.agents/skills/gstack-retro/SKILL.md index 88ec36e2..6d0bd5da 100644 --- a/.agents/skills/gstack-retro/SKILL.md +++ b/.agents/skills/gstack-retro/SKILL.md @@ -859,6 +859,28 @@ For each repo (sorted by commits descending): - Key work (inferred from commit messages) - AI sessions by tool +**Your Contributions** (sub-section within each project): +For each project, add a "Your contributions" block showing the current user's +personal stats within that repo. Use the user identity from `git config user.name` +to filter. Include: +- Your commits / total commits (with %) +- Your LOC (+insertions / -deletions) +- Your key work (inferred from YOUR commit messages only) +- Your commit type mix (feat/fix/refactor/chore/docs breakdown) +- Your biggest ship in this repo (highest-LOC commit or PR) + +If the user is the only contributor, say "Solo project — all commits are yours." +If the user has 0 commits in a repo (team project they didn't touch this period), +say "No commits this period — [N] AI sessions only." and skip the breakdown. + +Format: +``` +**Your contributions:** 47/244 commits (19%), +4.2k/-0.3k LOC + Key work: Writer Chat, email blocking, security hardening + Biggest ship: PR #605 — Writer Chat eats the admin bar (2,457 ins, 46 files) + Mix: feat(3) fix(2) chore(1) +``` + ### Cross-Project Patterns - Time allocation across projects (% breakdown) - Peak productivity hours aggregated across all repos diff --git a/autoplan/SKILL.md b/autoplan/SKILL.md index a2c74061..e95cfd18 100644 --- a/autoplan/SKILL.md +++ b/autoplan/SKILL.md @@ -38,6 +38,9 @@ _PROACTIVE=$(~/.claude/skills/gstack/bin/gstack-config get proactive 2>/dev/null _BRANCH=$(git branch --show-current 2>/dev/null || echo "unknown") echo "BRANCH: $_BRANCH" echo "PROACTIVE: $_PROACTIVE" +source <(~/.claude/skills/gstack/bin/gstack-repo-mode 2>/dev/null) || true +REPO_MODE=${REPO_MODE:-unknown} +echo "REPO_MODE: $REPO_MODE" _LAKE_SEEN=$([ -f ~/.gstack/.completeness-intro-seen ] && echo "yes" || echo "no") echo "LAKE_INTRO: $_LAKE_SEEN" _TEL=$(~/.claude/skills/gstack/bin/gstack-config get telemetry 2>/dev/null || true) @@ -138,6 +141,18 @@ AI-assisted coding makes the marginal cost of completeness near-zero. When you p - BAD: "Let's defer test coverage to a follow-up PR." (Tests are the cheapest lake to boil.) - BAD: Quoting only human-team effort: "This would take 2 weeks." (Say: "2 weeks human / ~1 hour CC.") +## Repo Ownership Mode — See Something, Say Something + +`REPO_MODE` from the preamble tells you who owns issues in this repo: + +- **`solo`** — One person does 80%+ of the work. They own everything. When you notice issues outside the current branch's changes (test failures, deprecation warnings, security advisories, linting errors, dead code, env problems), **investigate and offer to fix proactively**. The solo dev is the only person who will fix it. Default to action. +- **`collaborative`** — Multiple active contributors. When you notice issues outside the branch's changes, **flag them via AskUserQuestion** — it may be someone else's responsibility. Default to asking, not fixing. +- **`unknown`** — Treat as collaborative (safer default — ask before fixing). + +**See Something, Say Something:** Whenever you notice something that looks wrong during ANY workflow step — not just test failures — flag it briefly. One sentence: what you noticed and its impact. In solo mode, follow up with "Want me to fix it?" In collaborative mode, just flag it and move on. + +Never let a noticed issue silently pass. The whole point is proactive communication. + ## Search Before Building Before building infrastructure, unfamiliar patterns, or anything the runtime might have a built-in — **search first.** Read `~/.claude/skills/gstack/ETHOS.md` for the full philosophy.