fix: correct markdownlint errors in existing skill files
CI / lint (pull_request) Successful in 8s
CI / lint CI passed (push event context)

- sdlc-diagram.md: remove extra trailing blank line (MD012)
- sdlc/SKILL.md lines 76,91: add language to fenced code blocks (MD040)
- uat/SKILL.md: verify trailing newline (MD047)

These pre-existing issues were surfaced by the expanded CI introduced
in the 'ci: move to .gitea/workflows and expand lint coverage' commit.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
2026-05-21 11:27:11 +00:00
committed by Countess von Containerheim [agent]
parent 37fa23df15
commit 4dfc5f9ed9
3 changed files with 3 additions and 4 deletions
+2 -2
View File
@@ -73,7 +73,7 @@ Each promotion is a PR reviewed and merged by its gate owner:
### Pipeline A: Plugin/Feature Changes ### Pipeline A: Plugin/Feature Changes
``` ```text
Engineer → PR to dev → self-merge → deploys to dev Engineer → PR to dev → self-merge → deploys to dev
→ Engineer validates on dev → Engineer validates on dev
→ PR from dev → uat → QA reviews → QA merges → PR from dev → uat → QA reviews → QA merges
@@ -88,7 +88,7 @@ Applies to changes in `headlamp-*-plugin/` repos (plugin code, features, bug fix
### Pipeline B: Infrastructure Changes (No UI Impact) ### Pipeline B: Infrastructure Changes (No UI Impact)
``` ```text
Engineer → PR to main → CI passes → QA reviews → QA merges Engineer → PR to main → CI passes → QA reviews → QA merges
→ Production → Production
``` ```
-1
View File
@@ -132,4 +132,3 @@ flowchart LR
class UATB uat class UATB uat
class MAIN prod class MAIN prod
``` ```
+1 -1
View File
@@ -66,4 +66,4 @@ If `UAT_PLAYBOOK.md` does not exist for a plugin, treat that as a gap — report
- **Approve** the `uat→main` promotion when all applicable test steps from the playbook pass and no console errors are present - **Approve** the `uat→main` promotion when all applicable test steps from the playbook pass and no console errors are present
- **Request changes** when any test step fails — include specific failing steps, observed results vs. expected results, and failure screenshots - **Request changes** when any test step fails — include specific failing steps, observed results vs. expected results, and failure screenshots
- **Block** if the plugin fails to load entirely — escalate to CTO as a deployment issue requiring immediate resolution - **Block** if the plugin fails to load entirely — escalate to CTO as a deployment issue requiring immediate resolution