Skip to content

Feat/enel gict plugin#1668

Closed
gazzu wants to merge 3 commits into
github:mainfrom
ENEL-GICT-PTG:feat/enel-gict-plugin
Closed

Feat/enel gict plugin#1668
gazzu wants to merge 3 commits into
github:mainfrom
ENEL-GICT-PTG:feat/enel-gict-plugin

Conversation

@gazzu
Copy link
Copy Markdown

@gazzu gazzu commented May 11, 2026

Pull Request Checklist

  • I have read and followed the CONTRIBUTING.md guidelines.
  • I have read and followed the Guidance for submissions involving paid services.
  • My contribution adds a new instruction, prompt, agent, skill, or workflow file in the correct directory.
  • The file follows the required naming convention.
  • The content is clearly structured and follows the example format.
  • I have tested my instructions, prompt, agent, skill, or workflow with GitHub Copilot.
  • I have run npm start and verified that README.md is up to date.
  • I am targeting the staged branch for this pull request.

Description


Type of Contribution

  • New instruction file.
  • New prompt file.
  • New agent file.
  • New plugin.
  • New skill file.
  • New agentic workflow.
  • Update to existing instruction, prompt, agent, plugin, skill, or workflow.
  • Other (please specify):

Additional Notes


By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

@gazzu gazzu requested a review from aaronpowell as a code owner May 11, 2026 08:06
Copilot AI review requested due to automatic review settings May 11, 2026 08:06
@github-actions github-actions Bot added branched-main PR appears to include plugin files materialized from main targets-main PR targets main instead of staged labels May 11, 2026
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ This PR targets main, but PRs should target staged.

The main branch is auto-published from staged and should not receive direct PRs.
Please close this PR and re-open it against the staged branch.

You can change the base branch using the Edit button at the top of this PR,
or run: gh pr edit 1668 --base staged

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR introduces an enel-gict plugin with several new skill documents, but it also changes the repository’s canonical website URLs (README + llms.txt generator) to point at a fork-specific GitHub Pages site, which impacts published links and repository metadata.

Changes:

  • Updated the base website URL used in website/src/pages/llms.txt.ts and the repository README.
  • Added a new plugins/enel-gict directory containing multiple new skill definitions (RA/ADR/OP/design-system).

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 9 comments.

Show a summary per file
File Description
website/src/pages/llms.txt.ts Changes the website base used to generate llms.txt links and metadata.
README.md Rewrites many website links to a fork URL and introduces double-slash paths.
plugins/enel-gict/README.md Adds a new plugin README, but the plugin manifest/structure is incomplete for this repo’s plugin system.
plugins/enel-gict/skills/ra/SKILL.md Adds an RA authoring skill that references repo paths/workflows that don’t exist here.
plugins/enel-gict/skills/op/SKILL.md Adds an OP authoring skill that references non-existent repo structure and uses placeholder links.
plugins/enel-gict/skills/adr/SKILL.md Adds an ADR skill with assumptions/links that don’t match this repository’s actual contents.
plugins/enel-gict/skills/enel-design-system/SKILL.md Adds a design-system skill that references missing site tooling/config in this repo.

// Base URL for absolute links (to raw GitHub content)
const GITHUB_RAW_BASE = "https://raw.githubusercontent.com/github/awesome-copilot/main";
const WEBSITE_BASE = "https://awesome-copilot.github.com";
const WEBSITE_BASE = "https://enel-gict-ptg.github.io/awesome-copilot/";
content += "- **GitHub**: https://github.com/github/awesome-copilot\n";
content += "- **License**: MIT\n";
content += "- **Website**: https://awesome-copilot.github.com\n";
content += "- **Website**: https://enel-gict-ptg.github.io/awesome-copilot/\n";
Comment thread README.md
Comment on lines 6 to 12
> [!TIP]
> **Explore the full collection on the website →** [awesome-copilot.github.com](https://awesome-copilot.github.com)
> **Explore the full collection on the website →** [awesome-copilot.github.com](https://enel-gict-ptg.github.io/awesome-copilot/)
>
> The website offers full-text search and filtering across hundreds of resources, plus the [Tools](https://awesome-copilot.github.com/tools) section for MCP servers and developer tooling, and the [Learning Hub](https://awesome-copilot.github.com/learning-hub) for guides and tutorials.
> The website offers full-text search and filtering across hundreds of resources, plus the [Tools](https://enel-gict-ptg.github.io/awesome-copilot//tools) section for MCP servers and developer tooling, and the [Learning Hub](https://enel-gict-ptg.github.io/awesome-copilot//learning-hub) for guides and tutorials.
>
> **Using this collection in an AI agent?** A machine-readable [`llms.txt`](https://awesome-copilot.github.com/llms.txt) is available with structured listings of all agents, instructions, and skills.
> **Using this collection in an AI agent?** A machine-readable [`llms.txt`](https://enel-gict-ptg.github.io/awesome-copilot//llms.txt) is available with structured listings of all agents, instructions, and skills.

Comment thread README.md
Comment on lines 19 to +26
| Resource | Description | Browse |
|----------|-------------|--------|
| 🤖 [Agents](docs/README.agents.md) | Specialized Copilot agents that integrate with MCP servers | [All agents →](https://awesome-copilot.github.com/agents) |
| 📋 [Instructions](docs/README.instructions.md) | Coding standards applied automatically by file pattern | [All instructions →](https://awesome-copilot.github.com/instructions) |
| 🎯 [Skills](docs/README.skills.md) | Self-contained folders with instructions and bundled assets | [All skills →](https://awesome-copilot.github.com/skills) |
| 🔌 [Plugins](docs/README.plugins.md) | Curated bundles of agents and skills for specific workflows | [All plugins →](https://awesome-copilot.github.com/plugins) |
| 🪝 [Hooks](docs/README.hooks.md) | Automated actions triggered during Copilot agent sessions | [All hooks →](https://awesome-copilot.github.com/hooks) |
| ⚡ [Agentic Workflows](docs/README.workflows.md) | AI-powered GitHub Actions automations written in markdown | [All workflows →](https://awesome-copilot.github.com/workflows) |
| 🤖 [Agents](docs/README.agents.md) | Specialized Copilot agents that integrate with MCP servers | [All agents →](https://enel-gict-ptg.github.io/awesome-copilot//agents) |
| 📋 [Instructions](docs/README.instructions.md) | Coding standards applied automatically by file pattern | [All instructions →](https://enel-gict-ptg.github.io/awesome-copilot//instructions) |
| 🎯 [Skills](docs/README.skills.md) | Self-contained folders with instructions and bundled assets | [All skills →](https://enel-gict-ptg.github.io/awesome-copilot//skills) |
| 🔌 [Plugins](docs/README.plugins.md) | Curated bundles of agents and skills for specific workflows | [All plugins →](https://enel-gict-ptg.github.io/awesome-copilot//plugins) |
| 🪝 [Hooks](docs/README.hooks.md) | Automated actions triggered during Copilot agent sessions | [All hooks →](https://enel-gict-ptg.github.io/awesome-copilot//hooks) |
| ⚡ [Agentic Workflows](docs/README.workflows.md) | AI-powered GitHub Actions automations written in markdown | [All workflows →](https://enel-gict-ptg.github.io/awesome-copilot//workflows) |
Comment on lines +1 to +3
# Enel GICT Skills

Concise Enel GICT skill pack for Reference Architectures (RA), Architecture Decision Records (ADR), Operating Procedures (OP), and Enel Design System guidance to align delivery and governance.
Comment on lines +12 to +41
You are an expert enterprise architect for the GICT organization. Your job is to produce a complete Reference Architecture (RA) document following the exact template and conventions used in this repository, fully aligned with the organizational procedures in the `OP/` folder.

## When to Use This Skill

- User asks to write a new Reference Architecture
- User asks to draft an architecture document or blueprint for a technology domain
- User asks to update or review an existing RA in the catalog
- User mentions "create RA", "reference architecture", "architecture blueprint", or naming a technology domain
- User needs OP35/OP36 compliance sections filled in an architecture document

## Prerequisites

- This repository opened as the active workspace
- Familiarity with `docs/RA/` folder and existing RA catalog in `docs/index.md`
- Access to official documentation for technologies being evaluated (the skill will fetch these)

## Context

This workspace contains a catalog of Reference Architectures under `docs/`. Each RA follows a consistent numbered format (`NNN_RA_<slug>.md`) and covers a specific technology domain. The catalog index is maintained in [docs/index.md](in the source repository documentation/index.md).

RAs serve as standardized, opinionated blueprints for building modern cloud-native systems. They must be thorough, well-sourced, and actionable.

### Governing Organizational Procedures

Every RA produced in this repository must comply with two internal procedures:

- **[OP35 — Digital Initiatives Activation](../in the source repository documentation/OP35-Digital-Initiatives-Activation.md)** (v8, 28/05/2025): An RA IS the formal technical output of **narrative 6.0 — Evaluation of the technical solution of the initiative**. It must cover: technical alternatives and justification, high-level architecture, technical/functional impact on existing systems, cyber security high-level information, preliminary cost estimate, internal workforce needs, partners and technologies, macro plan. The RA must also contain the output of the **Buy or Make Decisional Framework** when a new digital initiative is involved.

- **[OP36 — Solutions Development & Release Management](../in the source repository documentation/OP36-Solutions-Development-Release-Management.md)** (v7, 11/12/2024): Mandates seven **design-by-default** compliance requirements that must be addressed in every RA before it can feed a Project narrative. These are: Cyber Security by Design (§4.6), Digital Accessibility/WCAG (§4.7), Personal Data Protection/GDPR (§4.8), Adoption by Design (§4.9), Quality Management (§4.11), Data Security in non-production (§4.12), and Intellectual Property by Design (§4.13).

Comment on lines +8 to +39
You are an expert process architect for the GICT organization. Your job is to produce, update, or reformat Organizational Procedure (OP) documents following the exact conventions used in this repository under `docs/OP/`.

## When to Use This Skill

- User asks to write, update, or review an Organizational Procedure
- User asks to reformat an OP from PDF to clean markdown
- User asks to cross-reference OP requirements into RA or ADR documents
- User mentions "OP", "organizational procedure", "reformat OP", "PDF to markdown", or "OP35"/"OP36"

## Prerequisites

- This repository opened as the active workspace
- Source document (PDF text dump, Word export, or original content) if creating/reformatting
- Familiarity with `docs/OP/` folder and existing OPs

## Context

This repository maintains Organizational Procedures under `docs/OP/`. OPs define roles, responsibilities, and operating methods for GICT processes within the Enel Group. They are **governing documents** that Reference Architectures (RAs) and Architecture Decision Records (ADRs) must comply with.

### Current OPs

| Document | Version | Scope |
|----------|---------|-------|
| [OP35 — Digital Initiatives Activation](in the source repository documentation/OP/OP35-Digital-Initiatives-Activation.md) | v8, 28/05/2025 | Investment activation, Buy/Make framework, initiative approval |
| [OP36 — Solutions Development & Release Management](in the source repository documentation/OP/OP36-Solutions-Development-Release-Management.md) | v7, 11/12/2024 | SDRM lifecycle, design-by-default compliance, Project/Change/Corrective processes |

### Relationship to Other Document Types

- **RA documents** (`docs/RA/`) reference OPs for compliance: OP35 §6.0 governs initiative technical evaluation; OP36 §4.6–§4.13 mandates seven design-by-default requirements.
- **ADR documents** (`docs/ADR/`) reference OPs for Buy/Make decisions and compliance checklists.
- When updating an OP, check whether downstream RA or ADR templates need corresponding updates.

Comment on lines +21 to +37
- This repository opened as the active workspace
- Familiarity with `docs/ADR/` folder and existing ADRs
- Access to official documentation for candidate tools/vendors (the skill will fetch these)

## Context

This repository maintains ADRs and gap analyses under `docs/ADR/`. These documents record technology choices, vendor evaluations, open-source versus proprietary assessments, and buy-or-make decisions.

ADRs in this repository operate within two governing Organizational Procedures:

- **[OP35 — Digital Initiatives Activation](in the source repository documentation/OP35-Digital-Initiatives-Activation.md)**: Mandates a "Buy or Make Decisional Framework" (narrative 6.0) and requires TA&CS Delivery/T&A involvement for all technical evaluations at initiative activation.
- **[OP36 — Solutions Development & Release Management](in the source repository documentation/OP36-Solutions-Development-Release-Management.md)**: Requires design-by-default compliance across Cyber Security, Digital Accessibility (WCAG), Personal Data Protection (GDPR/DPIA), Intellectual Property, Adoption, and Quality Management for all Projects and Changes.

## Before You Start

1. **Read existing ADRs** — scan `docs/ADR/` to understand conventions and avoid duplication.
2. **Ask clarifying questions** — use the ask-questions tool to gather at minimum:
Comment on lines +15 to +32
## Prerequisites

- This repository opened as the active workspace
- `zensical.toml` at repository root with `[project.theme]` section
- `docs/stylesheets/extra.css` for CSS overrides

## Reference

- Design System Storybook: `https://eneldesignsystem-dev.enelint.global`
- Tokens extracted from: `https://www.enel.com` corporate CSS bundle

## Scope

- Theme config: `zensical.toml` — `[project.theme]` section
- CSS overrides: `docs/stylesheets/extra.css`
- Logo image: `docs/assets/images/enel-logo.png`
- Template overrides: `overrides/` directory

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branched-main PR appears to include plugin files materialized from main targets-main PR targets main instead of staged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants