fix: Capability Skill Github Actions Automation - #1072
Conversation
…dded github actions support.
✅ Deploy Preview for common-cloud-controls canceled.
|
|
@zigmax it would be great if we could automate the threats analysis in the same way. Can you take a look at writing some skills for this? |
|
You can see the result of this working on my fork: robmoffat#2 |
|
Hi @robmoffat, I'm ok with splitting the skill. But it has very tight coupling, which I believe is unnecessary. For example. I have committed the metadata file to the repo. Now I want to use the Github action / skill to create the capabilities.yaml but unable to do that because I do not have an open PR to commit the metadata.yml |
|
|
||
| - `example_service` and `source_cloud` are supplied in the prompt wrapper — do not ask for them. | ||
| - Do **not** wait for CONFIRM or EDIT; complete all assigned steps in one response. | ||
| - **Call A (Step 1 only):** return **JSON only** (no markdown, no prose): |
There was a problem hiding this comment.
Where is "Call A" defined? And what is the use of it?
| } | ||
| ``` | ||
|
|
||
| - **Call B (Steps 2–4):** return exactly two parts: |
There was a problem hiding this comment.
Where i "Call B defined? And what is the use of it?
| - Do **not** modify `metadata.yaml`. | ||
| - Return **raw YAML only** for `capabilities.yaml` (no markdown fences, no commentary). File must validate against `schemas/capabilities-schema.json`. | ||
|
|
||
| Companion files appended below this skill: PR-branch `metadata.yaml`, `schemas/capabilities-schema.json`, `style-guides/catalogs/capability-style-guide.yaml`, core capability id+title index, and an example `capabilities.yaml`. |
There was a problem hiding this comment.
This is missing core capabilities file as a companion file.
I can't see where capabilities.yaml file is provided as an example in this SKILL. May be I understood it wrong.
What do you suggest? |
|
Hi Sonali, I think I've addressed your issues above. It had made a bit of a dog's breakfast splitting them in two which I hadn't anticipated. You can use the skills in GHA: And also from cursor: 
|
I think we should ask the |
|
Hi Maxime, thanks for approving. I actually think I need to update this PR now you have written your skills. So I won't merge yet |
|
This issue will be closed as stale in 7 days. If this issue is blocked, |
3 participants
This pull request introduces a new two-phase automation for creating and validating CCC capability catalogues using GitHub Actions workflows and supporting skills documentation. The workflows automate the creation of draft
metadata.yamlfiles for new catalogues and the generation of validatedcapabilities.yamlfiles after human review, streamlining the catalogue onboarding process.This splits the SKILL.md written by @smendis-scottlogic into two parts, in order to avoid the user interaction step in the middle.
The most important changes are:
New GitHub Actions Workflows:
.github/workflows/draft-catalogue-metadata.ymlto automate the creation of a draft catalogue folder andmetadata.yamlusing an LLM, based on an example service and source cloud. The workflow validates URLs, generates folder structure, and opens a draft PR for review..github/workflows/add-catalogue-capabilities.ymlto automate the generation ofcapabilities.yamlfor a catalogue that already has a reviewedmetadata.yaml. The workflow validates the output, commits the new file, and comments on the PR when ready for review.Supporting Skill Documentation:
skills/create-capability-catalogue-metadata/SKILL.md, detailing the step-by-step process for generating cross-cloud mappings andmetadata.yaml, with explicit instructions for both interactive and GitHub Actions modes.skills/create-capability-catalogue-capabilities/SKILL.md, specifying the process for generatingcapabilities.yamlfrom confirmed metadata, including schema validation and formatting rules for both interactive and GitHub Actions modes.Workflow Improvements:
.github/workflows/yaml_check.ymlto accept a git ref input and useactions/checkout@v4, allowing validation of YAML files on specific branches as part of the new workflows.How It Works
Once this PR is merged to main (I did this in my robmoffat/common-cloud-controls fork), you get two new Github Actions:
Running the "Draft Catalog Metadata" one will create a branch containing the metadata which you can review. It also creates a PR if the action is merged to the main of FINOS/common-cloud-controls - this doesn't work on my fork.
You can then review the PR and make sure it gets all the details correct (@smendis-scottlogic you had this in an interactive session, but that won't work with GHA, hence the split to two skills).
Once you have reviewed the PR, you run the second action:
And once that completes the PR will have the capabilities in to review too: