Chrome Extension Release: From Merged PR to Web Store Update

    1

    A guided release checklist for Chrome extensions: checks, permission and privacy review, version bump, git tag, GitHub release and Chrome Web Store upload.

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Chrome Extension Release: From Merged PR to Web Store Update

    Example session with this skill installed

    I'm a senior dev joining this Go project. Explain the architecture and write a report using parallel subagents.

    • Read your context and instructions
    • Compiled the chrome extension release

    I have analyzed the project structure using parallel subagents for the core modules. The architecture report has been generated to provide a high-level view of the system, including service boundaries and data flow.

    Architecture Report — GopherCommerce

    Generated: 2023-10-27
    Seniority level: Senior

    1. Project Overview

    GopherCommerce is a microservices-based e-commerce backend built in Go. It handles product catalogs, order processing, and user authentication using a modular monolith approach transitioning to full microservices.

    2. Technology Stack

    technologyversionpurposewhy chosen
    Go1.21Core LanguagePerformance and concurrency
    PostgreSQL15Primary DatabaseRelational integrity
    Redis7CachingLow-latency session storage
    gRPCv1.58Internal RPCType-safe service communication

    3. High-Level Architecture

    • Architecture style: Modular Monolith
    • ASCII Diagram:
      [API Gateway] --> [Auth Module]
      
           |
      
           +----------> [Catalog Module] --> [Postgres]
      
           |
      
           +----------> [Order Module]   --> [Postgres]
                                         --> [Redis]
      

    4. Module Breakdown

    Catalog Module
    • Purpose: Manages product lifecycle and inventory.
    • Structure: Clean Architecture (cmd, internal/domain, internal/repository).
    • Key files: internal/catalog/service.go (business logic), internal/catalog/repo.go (SQL queries).
    • External calls: None.

    5. End-to-End Request Flow

    Operation: User creates a product.

    1. cmd/api/main.go: Router catches POST /products.
    2. internal/catalog/handler.go: Decodes JSON and validates input.
    3. internal/catalog/service.go: Executes CreateProduct logic.
    4. internal/catalog/repository.go: Persists data to products table.

    6. Potential Pain Points

    • Coupling: The Order module directly imports the User domain, complicating a future service split.
    • Database: Product queries lack composite indexes for the most common search filters.

    Next steps

    • Review the full report in docs/architecture.md.
    • Ask me to trace the Checkout flow across modules.
    • Request a deep dive into the Auth middleware implementation.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Releasing an extension is more than npm version. Permissions changes can disable the extension for existing users, the Privacy practices tab must match what the code does, and store listings live in several languages. This skill walks your agent through the whole release and stops for your approval before anything leaves your machine.

    What you get

    • Pre-release checks driven by your own package.json scripts.
    • A manifest diff since the last tag, with every added permission called out, and a table of which docs and store texts to review for which kind of change.
    • Version bump and annotated tag, with the Chrome Web Store version rules explained.
    • Push and GitHub release steps that ask first.
    • A clear hand-off for the manual Web Store dashboard steps.

    Example prompts

    • "Release a patch version"
    • "Prepare v1.4.0 for the Chrome Web Store"
    • "What changed in permissions since the last release?"

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.

    Requires build manifests (e.g., package.json, go.mod) to identify the stack. Performance on massive monorepos depends on subagent availability.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 17 days ago

    • Free with an Agensi account

    Software
    Git

    Permissions

    Read Files
    Write Files
    Listed17 days ago

    What's inside

    Frequently Asked Questions

    The skill offers three distinct profiles (Beginner, Intermediate, Senior), adjusting the level of technical abstraction, the complexity of trade-off analysis, and the use of analogies to match the reader's expertise.

    This skill is designed for use within AI IDEs and agents that have file-system access; it automatically detects your stack by scanning manifests like package.json or go.mod, requiring no manual configuration.

    For large-scale monorepos, the skill utilizes parallel subagents to audit multiple modules simultaneously, ensuring comprehensive coverage without hitting token limits or time-out errors.

    You receive the full architecture analysis skill, including the specialized subagent workflow for parallel processing and a template library for generating the ASCII diagrams and Markdown reports.

    Unlike a simple prompt, this skill executes a multi-step discovery process that verifies real file dependencies and request flows, preventing the hallucinations and path errors common in generic AI chats.

    New in DevOps & Cloud

    Free