.claude/skills/chrome-github/SKILL.md
# CHROME-GITHUB-PR SKILL **Skill Name**: chrome-github-pr **Version**: 1.0.0 **Trigger**: `/chrome-github`, "open github pr", "review pr in browser", "check github actions" **Description**: Navigate GitHub in Chrome to create PRs, review diffs, check Actions CI status, and merge branches when the `gh` CLI is unavailable or when visual diff review is needed. --- ## SKILL PURPOSE Provide browser-based GitHub workflow automation for the CCW-CRM repository — PR creation, CI monitoring, diff revi
npx skillsauth add CleanExpo/CCW-CRM .claude/skills/chrome-githubInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Skill Name: chrome-github-pr
Version: 1.0.0
Trigger: /chrome-github, "open github pr", "review pr in browser", "check github actions"
Description: Navigate GitHub in Chrome to create PRs, review diffs, check Actions CI status, and merge branches when the gh CLI is unavailable or when visual diff review is needed.
Provide browser-based GitHub workflow automation for the CCW-CRM repository — PR creation, CI monitoring, diff review, and merging — as an alternative or supplement to gh CLI commands.
Trigger phrases:
/chrome-githubmcp__Claude_in_Chrome__navigate: https://github.com/[owner]/CCW-CRM
Screenshot to confirm repo and login:
mcp__Claude_in_Chrome__computer: { action: "screenshot" }
If not logged in or wrong repo → stop and correct.
Navigate to Pull Requests tab:
mcp__Claude_in_Chrome__navigate: https://github.com/[owner]/CCW-CRM/pulls
mcp__Claude_in_Chrome__get_page_text
List open PRs:
| PR # | Title | Author | CI Status | Reviews |
|-------|------------------------------|---------|-----------|---------|
| #123 | feat: add video pipeline | user | PASSING | 0 |
Navigate to a specific workflow run:
mcp__Claude_in_Chrome__navigate: https://github.com/[owner]/CCW-CRM/actions
mcp__Claude_in_Chrome__get_page_text
Find the latest run for the current branch. Extract:
If failing, click through to the specific job → step → copy error lines.
Requires user confirmation before submission.
Navigate to compare page:
mcp__Claude_in_Chrome__navigate: https://github.com/[owner]/CCW-CRM/compare/[branch]
Fill in PR details:
mcp__Claude_in_Chrome__form_input: { selector: "#pull_request_title", text: "[title]" }
mcp__Claude_in_Chrome__form_input: { selector: "#pull_request_body", text: "[description]" }
PR description template:
## Summary
- [bullet point changes]
## Test plan
- [ ] TypeScript: `pnpm turbo run type-check` passes
- [ ] Tests: `pnpm turbo run test` passes
- [ ] Visual: production site checked
🤖 Generated with Claude Code
Pause before clicking "Create pull request": "Ready to create the PR. Review the title and description above, then confirm."
After user confirms:
mcp__Claude_in_Chrome__computer: { action: "click", coordinate: [submit-button] }
mcp__Claude_in_Chrome__computer: { action: "screenshot" }
Report: PR number and URL.
Navigate to Files Changed tab:
mcp__Claude_in_Chrome__computer: { action: "click", coordinate: [files-changed-tab] }
mcp__Claude_in_Chrome__get_page_text
Summarise:
Requires explicit user confirmation.
"Ready to merge PR #[N] via [merge strategy]. This cannot be undone. Confirm?"
After confirmation:
mcp__Claude_in_Chrome__computer: { action: "screenshot" }
After PR creation:
After merge:
Version: 1.0
Created: April 2026
Tools: mcp__Claude_in_Chrome__*
content-media
Autonomously uploads CCW HeyGen demo videos to YouTube as Unlisted, collects video IDs, and patches DemoVideoBanner.tsx + video-registry.json. One-time OAuth setup required. Handles resume, retries, and ID propagation.
data-ai
Clear the freeze boundary set by /freeze, allowing edits to all directories again. Use when you want to widen edit scope without ending the session. Use when asked to "unfreeze", "unlock edits", "remove freeze", or "allow all edits". (gstack)
tools
# Spec Interview Skill **Name:** spec-interview **Triggers:** `/spec-interview`, when requirements unclear **Version:** 1.0.0 --- ## Purpose Interviews user to gather complete requirements before planning. --- ## Interview Questions When requirements are unclear, ask: ### 1. Feature Clarity **Question:** "What is this feature supposed to do?" **Why:** Need clear objective ### 2. User Impact **Question:** "Who will use this and why?" **Why:** Understand user needs ### 3. Success Criteri
development
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy", "push to main", "create a PR", "merge and push", or "get it deployed". Proactively invoke this skill (do NOT push/PR directly) when the user says code is ready, asks about deploying, wants to push code up, or asks to create a PR. (gstack)