google-spaces-updates

⚠Review·Scanned 2/18/2026

Posts project updates to Google Chat Spaces via webhook, reading config from .claude/settings.json and using templates in templates/. It requests/stores the webhook URL (https://chat.googleapis.com/v1/spaces/SPACE_ID/messages?key=API_KEY&token=TOKEN), runs local shell/git commands (cat .claude/settings.json, git log) and posts via curl.

by jezweb·v10a1f16·13.0 KB·305 installs
Scanned from main at 10a1f16 · Transparency log ↗
$ vett add jezweb/claude-skills/google-spaces-updatesReview findings below

Google Spaces Updates

Post team updates to Google Chat Spaces via webhook.

Auto-trigger keywords

  • "post to team", "notify team", "update the team"
  • "tell Deepinder", "tell Joshua", "tell Raquel"
  • "google spaces", "team chat"
  • After deployments, major features, or when asking questions

What this skill does

  1. Reads project config from .claude/settings.json
  2. Formats messages based on update type
  3. Posts to Google Spaces webhook with rich formatting
  4. Includes relevant context (commits, URLs, files changed)

Commands

CommandPurpose
/google-spaces-updates setupCreate settings.json for current project
/google-spaces-updates deploymentPost deployment notification
/google-spaces-updates bugfixPost bug fix notification
/google-spaces-updates featurePost feature completion
/google-spaces-updates questionAsk team a question
/google-spaces-updates custom "message"Post custom message

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

Prerequisites

Project must have .claude/settings.json with:

{
  "project": { "name": "...", "repo": "..." },
  "team": { "chat_webhook": "https://chat.googleapis.com/v1/spaces/..." }
}

Run /google-spaces-updates setup to create this file interactively.

Testing

For developing new formats or debugging, use the test space webhook in test-config.json instead of posting to real team spaces.