Google Spaces Updates

Quick Start

1. Setup (first time per project)

/google-spaces-updates setup

.claude/settings.json

{
  "project": {
    "name": "my-project",
    "repo": "github.com/org/my-project"
  },
  "team": {
    "chat_webhook": "https://chat.googleapis.com/v1/spaces/SPACE_ID/messages?key=KEY&token=TOKEN",
    "members": ["Deepinder", "Joshua", "Raquel"]
  }
}

2. Post an update

"Post deployment update to team"
"Tell the team about the new feature"
"Ask the team about the auth approach"

How It Works

Step 1: Check for project settings

.claude/settings.json

cat .claude/settings.json 2>/dev/null || echo "NOT_FOUND"

"This project doesn't have Google Spaces configured. Would you like me to set it up? I'll need the webhook URL for your team's Google Space."

templates/settings-template.json

Step 2: Determine update type

deployment

bugfix

feature

question

custom

Step 3: Gather context

# Recent commits (for context)
git log --oneline -3 2>/dev/null

# Current branch
git branch --show-current 2>/dev/null

# Changed files (if recent changes)
git diff --name-only HEAD~1 2>/dev/null | head -10

• What was just completed
• Any preview/production URLs
• Relevant file paths
• Who might need to know

Step 4: Format the message

templates/

• Use

  *bold*

  for emphasis (not markdown bold)
• Use

  _italic_

  for secondary text
• Newlines work as expected
• Keep messages concise but informative
• Include actionable links when relevant

Step 5: Post to webhook

curl -X POST "WEBHOOK_URL" \
  -H "Content-Type: application/json" \
  -d '{"text": "MESSAGE_HERE"}'

• WEBHOOK_URL

  with value from

  .claude/settings.json

  →

  team.chat_webhook

• MESSAGE_HERE

  with the formatted message (escape quotes properly)

Step 6: Confirm to user

"Posted update to team chat: [brief summary of what was posted]"

Message Templates

Deployment

🚀 *Deployed: [PROJECT_NAME]*

[WHAT_CHANGED - 1-2 sentences]

• Branch: `[BRANCH]`
• Commit: `[COMMIT_HASH]`
[• Preview: URL (if applicable)]
[• Production: URL (if applicable)]

_Posted by [USER] via Claude Code_

Bug Fix

🐛 *Bug Fixed: [PROJECT_NAME]*

*Problem:* [What was broken]
*Solution:* [How it was fixed]
*Files:* [Key files changed]

[• Commit: `[COMMIT_HASH]`]

_Please verify if you reported this issue._

Feature Complete

✨ *Feature Complete: [PROJECT_NAME]*

*[FEATURE_NAME]*

[DESCRIPTION - what it does, 1-2 sentences]

[• Demo: URL]
[• Files: key files]

_Ready for review/testing._

Question

❓ *Question: [PROJECT_NAME]*

[QUESTION - clear and specific]

*Context:*
[Relevant background - what you're working on, what you've tried]

*Options considered:*
1. [Option A]
2. [Option B]

_@[PERSON] - would appreciate your input_

Custom

📢 *Update: [PROJECT_NAME]*

[MESSAGE]

_Posted by [USER] via Claude Code_

Setup Command

/google-spaces-updates setup

1. Ask for the Google Spaces webhook URL
2. Ask for project name (or detect from package.json/repo)
3. Ask for team members (optional)
4. Create

   .claude/settings.json

   using the template
5. Add

   .claude/

   to

   .gitignore

   if not already there
6. Confirm setup is complete

Proactive Suggestions

• User says "done", "finished", "completed" after significant work
• After a

  git push

  to main/master/production
• User mentions team members by name
• User seems blocked and might benefit from team input

When NOT to Use

• Minor refactors, typo fixes
• WIP commits that aren't ready for review
• Internal debugging/testing
• Anything that would just be noise

Getting a Webhook URL

1. Open Google Chat
2. Navigate to your Space
3. Click Space name → Apps & integrations → Webhooks
4. Click Add webhook
5. Name it (e.g., "Claude Code Updates")
6. Copy the webhook URL

https://chat.googleapis.com/v1/spaces/SPACE_ID/messages?key=KEY&token=TOKEN

.claude/settings.json

.gitignore