Rename skills and added documentation for skills (#117)

* Rename skills and added documentation for skills

Author: haroonc

README.md

@@ -14,10 +14,11 @@ The CI/CD extension for Gemini CLI automates Continuous Integration and Continuo
 
 ## 📋 Key Features
 
--   **Intelligent Code Deployment**: Use the `/cicd:deploy` command to deploy your codebase. The extension leverages Gemini to analyze your project and recommend the best Google Cloud service: Cloud Run for dynamic applications or Cloud Storage for static websites. Includes pre-deployment scanning for secrets, keys, and passwords to prevent accidental leaks.
--   **AI-Powered CI/CD Pipeline Design**: Generate secure and robust CI/CD pipelines in moments with `/cicd:design`. Collaborate with Gemini to tailor the pipeline to your specific needs, including automatic setup of the required Google Cloud infrastructure.
--   **Interactive GCP Management**: The extension provides commands and tools to interact directly with Google Cloud's CI/CD services (Cloud Build, Artifact Registry, Artifact Analysis, Cloud Deploy, Developer Connect) from within Gemini CLI. Run builds, check for vulnerabilities (CVEs), view SBOMs, and pull build logs to investigate failures.
--   **Simplified Complex Release Flows**: Build sophisticated Cloud Deploy release pipelines quickly, guided by simple, interactive questions.
+-   **Intelligent Code Deployment**: Use the `google-cicd-deploy` skill to deploy your codebase. The extension leverages Gemini to analyze your project and deploy to Google Cloud services like Cloud Run for dynamic applications or Cloud Storage for static websites. Includes pre-deployment secret scanning.
+-   **AI-Powered CI/CD Pipeline Design**: Generate secure and robust CI/CD pipelines with `google-cicd-pipeline-design`. Collaborate with Gemini to tailor the pipeline and generate a YAML configuration.
+-   **Terraform GCP Infrastructure**: Provision and troubleshoot production-grade Google Cloud infrastructure using the `google-cicd-terraform` skill, enforcing Google’s Cloud Foundation Fabric patterns.
+-   **Interactive GCP Management**: The extension provides tools to interact directly with Google Cloud's CI/CD services (Cloud Build, Artifact Registry, Cloud Deploy, Developer Connect) from within Gemini CLI.
+-   **Simplified Complex Release Flows**: Build sophisticated Cloud Deploy release pipelines with the `google-cicd-release-orchestration` skill, setting up deployment strategies like canary and automatic rollbacks.
 -   **Integrated CI/CD MCP Server**: The extension includes a local Model Context Protocol (MCP) server, seamlessly integrating Gemini CLI with Google Cloud CI/CD services.
 
 ## ⚙️ Installation
@@ -40,8 +41,10 @@ gemini extensions install https://github.com/gemini-cli-extensions/cicd
     *   Artifact Registry API
     *   Artifact Analysis API
     *   Developer Connect API
-    *   Cloud Run API
+    *   Cloud Resource Manager API
     *   Cloud Storage API
+    *   Cloud Run API
+    *   Google Kubernetes Engine API
 *   Application Default Credentials (ADC): Ensure [Application Default Credentials](https://cloud.google.com/docs/authentication/gcloud) are configured in your environment. You can set this up by running:
     ```bash
     gcloud auth login
@@ -56,8 +59,8 @@ gemini extensions install https://github.com/gemini-cli-extensions/cicd
 > This CI/CD extension connects Gemini CLI to a local MCP server, granting it the ability to access and modify your Google Cloud data based on your Application Default Credentials.
 >
 > *   **LLM Hallucinations & Unintended Actions:** LLMs can produce incorrect or unexpected outputs ("hallucinate"). Since this extension allows Gemini to call tools that modify cloud resources, hallucinations can lead to unintended actions on your GCP project. **Always meticulously verify all generated configurations and commands before execution.**
-> *   **Authentication and Permissions (ADC):** The extension uses your local ADC, inheriting its permissions. Be aware of the scope of these permissions, as Gemini CLI can potentially read, modify, and delete GCP resources.
-> *   **Pipeline Service Account Permissions:** CI/CD pipelines generated by `/cicd:design` run using a GCP service account. Carefully vet the IAM roles and permissions assigned to this service account to prevent overly broad access.
+> *   **Authentication and Permissions:** The extension uses your local Application Default Credentials ([ADC](https://docs.cloud.google.com/docs/authentication/set-up-adc-local-dev-environment)), inheriting its permissions. Be aware of the scope of these permissions, as Gemini CLI can potentially read, modify, and delete GCP resources.
+> *   **Pipeline Service Account Permissions:** CI/CD pipelines generated by the `google-cicd-pipeline-design` skill run using a GCP service account. Carefully vet the IAM roles and permissions assigned to this service account to prevent overly broad access.
 > *   **Indirect Prompt Injection Risk:** Be cautious when providing input to the language model, especially from untrusted sources, due to the risk of indirect prompt injection.
 > *   **Untrusted Inputs:** Never include untrusted inputs (e.g., files, documents, emails from unverified sources) in the model's context. Such inputs could contain hidden instructions to hijack your session.
 > *   **Untrusted Tools:** Only use this extension with the official tools it provides.
@@ -66,25 +69,36 @@ gemini extensions install https://github.com/gemini-cli-extensions/cicd
 
 ## ☕ Usage
 
-#### `/cicd:deploy`
-Analyzes your local workspace to recommend and guide you through deploying to the most suitable Google Cloud service. It suggests Cloud Storage for static websites and Cloud Run for dynamic applications. Includes a pre-deployment scan for secrets to help prevent leaks.
+Activate the specialized skills using the `activate_skill` tool or by asking Gemini to use them.
+
+#### `google-cicd-deploy`
+Deploys your application to Google Cloud. Analyzes your workspace and deploys to Cloud Storage for static websites or Cloud Run for container-based applications (either via Buildpacks or by building an image). Includes a pre-deployment scan for secrets to help prevent leaks.
 
-#### `/cicd:design`
-Launches an AI-assisted process to design and generate a CI/CD pipeline configuration (`cloudbuild.yaml`) tailored to your project, including the necessary Google Cloud infrastructure.
+#### `google-cicd-pipeline-design`
+Designs and implements a Google Cloud-based CI/CD pipeline. Operates in two stages:
+1.  **Architectural Design**: Gathers context, proposes deployment patterns, and drafts a YAML action plan collaboratively.
+2.  **Plan Implementation**: Translates the approved plan into Terraform HCL or implements it directly using specialized tools and `gcloud`.
 
 **Design Process:**
 
 1.  **Requirement Gathering:** Gemini inspects your current workspace and asks clarifying questions to understand your application type, build process, testing strategies, and deployment objectives.
-2.  **Infrastructure Setup:** Based on the requirements, Gemini guides you through setting up the required GCP resources. This may include:
+2.  **Infrastructure Setup:** Based on the requirements, Gemini guides you through setting up the required GCP resources. The skill offers setting up infrastructure using Terraform or directly updating your Google Cloud resources. This may include:
     *   Creating or configuring Artifact Registry repositories.
     *   Establishing connections to your Git repository (e.g., GitHub) using Developer Connect.
     *   Setting up or advising on necessary IAM service accounts and permissions for the Cloud Build service.
+
 3.  **Pipeline Configuration Generation:** Gemini generates a `cloudbuild.yaml` file defining the pipeline stages (e.g., source checkout, build, test, artifact push). The configuration uses Cloud Build's script mode for clarity and ease of editing.
 4.  **Validation & Testing:** The extension will attempt to validate the generated pipeline configuration, potentially by submitting an initial test build using `gcloud builds submit`.
 5.  **Review & Refinement:** You can review the generated configuration and infrastructure setup and provide feedback to Gemini for adjustments.
 
 The goal is to produce a functional, production-ready CI/CD pipeline configuration with all the necessary GCP prerequisites in place.
 
+#### `google-cicd-release-orchestration`
+Designs Cloud Deploy delivery pipelines and manages releases. Guides you through designing `clouddeploy.yaml` for targets, pipelines, and automations (including observability alert policies). Also assists with release management and generating runtime manifests.
+
+#### `google-cicd-terraform`
+Architects, provisions, and troubleshoots CI/CD related resources in Google Cloud infrastructure using Terraform. Provides expert guidance on designing and deploying core services (Cloud Build, Cloud Deploy, Artifact Registry), implementing IAM least-privilege, and managing GCS-backed state.
+
 ### 🛠️ Supported MCP Tools
 
 The extension exposes the following tools to Gemini CLI, enabling interaction with Google Cloud services:

skills/gcp-cicd-deploy/SKILL.md skills/google-cicd-deploy/SKILL.mdskills/gcp-cicd-deploy/SKILL.md renamed to skills/google-cicd-deploy/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: deploy-cicd-gcp
+name: google-cicd-deploy
 description: Deploy an application to Google Cloud. Use when the user wants to deploy a new application on GCP.
 ---
 

…nces/how_to_deploy_to_gcs_with_gcloud.md …nces/how_to_deploy_to_gcs_with_gcloud.mdskills/gcp-cicd-deploy/references/how_to_deploy_to_gcs_with_gcloud.md renamed to skills/google-cicd-deploy/references/how_to_deploy_to_gcs_with_gcloud.md skills/gcp-cicd-deploy/references/how_to_deploy_to_gcs_with_gcloud.md renamed to skills/google-cicd-deploy/references/how_to_deploy_to_gcs_with_gcloud.md

@@ -1,5 +1,5 @@
 ---
-name: gcp-cicd-design
+name: google-cicd-pipeline-design
 description: Design and implement a Google Cloud based CI/CD pipeline. Use when the user wants to build a new pipeline, design an architecture on GCP.
 ---
 
@@ -39,12 +39,12 @@ Once the user has approved the YAML plan, you must guide them through the implem
 
 2.  **Execute Based on Choice**:
     *   **If Terraform is selected**:
-        *   Activate the `gcp-cicd-terraform` skill.
+        *   Activate the `google-cicd-terraform` skill.
         *   Translate the approved YAML plan into Terraform HCL, following the standards and structure defined in the skill.
         *   Follow the skill's **Execution Protocol** (Init, Validate, Plan, Apply), ensuring manual confirmation before the final `apply`.
     *   **If Direct Implementation is selected**:
         *   **Process Sequentially**: Execute the plan by processing the `stages` object in order.
-        *   **Leverage Skills & Tools**: For each component, check for available specialized tools (e.g., `create_cloud_build_trigger`) or relevant skills (e.g., `cloud-deploy-pipelines`). If a matching tool or skill is found, prioritize its use.
+        *   **Leverage Skills & Tools**: For each component, check for available specialized tools (e.g., `create_cloud_build_trigger`) or relevant skills (e.g., `google-cicd-release-orchestration`). If a matching tool or skill is found, prioritize its use.
         *   **GCloud Fallback**: If no specialized tool or skill exists for a component, fall back to the appropriate `gcloud` command via `run_shell_command`.
         *   **Report & Progress**: Announce the start of each step, wait for success, and report completion before proceeding to the next component.