corp-v1-3darch-skills-code-agent/corp-v1-channel-releases-3darch
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request 'feat: include UI/UX in Corp v1 channel coordination' (#1) from feat/ui-ux-channel-sync into test

Browse Source
This commit is contained in:
jarvis-at-skic
2026-08-25 01:18:39 -07:00
parent c5d7d5da47 ccbce7eff1
commit 12891cf409
1 changed files with 7 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
SKILL.md
+7 -2
View File
@@ -14,7 +14,7 @@ metadata:
## Overview
This skill owns release readiness and the controlled release-change workflow for a Corp v1 project. It monitors the project's `general`, `scope`, `architecture`, `kanban`, `delivery`, and `releases` channels for release implications, but it starts release execution only after an explicit team request.
This skill owns release readiness and the controlled release-change workflow for a Corp v1 project. It monitors the project's `general`, `scope`, `architecture`, `ui-ux`, `kanban`, `delivery`, and `releases` channels for release implications, but it starts release execution only after an explicit team request.
Load the global `documentation-docusaurus` skill from `https://gitea.lego-cloud.eu/home-v1-skills-code-agent/documentation-docusaurus` before changing documentation structure, navigation, Markdown/MDX, Docusaurus configuration, or builds.
@@ -60,12 +60,13 @@ Inspect only:
corp-v1-<code>-general
corp-v1-<code>-scope
corp-v1-<code>-architecture
corp-v1-<code>-ui-ux
corp-v1-<code>-kanban
corp-v1-<code>-delivery
corp-v1-<code>-releases
```
Use mapped-channel history to avoid duplicate work and new relevant activity from the other five channels. Never inspect another project's channels.
Use mapped-channel history to avoid duplicate work and new relevant activity from the other six channels. Never inspect another project's channels.
## Release Readiness
@@ -161,6 +162,10 @@ When separately authorized after approval:
Never claim deployment from a merged PR alone.
## UI/UX Coordination
For frontend-affecting releases, Releases verifies the approved UI/UX acceptance evidence and records production design regressions or user-feedback deltas for the `ui-ux` channel. Release approval and deployment remain owned by Releases.
## Synchronization Workflow
1. Read new same-project activity and enough release history to avoid duplicates.