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

fix: update Corp v1 skill references

Browse Source
This commit is contained in:
jarvis-at-skic
2026-09-04 12:55:02 +00:00
parent 94d147880f
commit 1297bfd89f
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
SKILL.md
+3 -3
View File
@@ -7,7 +7,7 @@ license: MIT
metadata: metadata:
hermes: hermes:
tags: [corp-v1, discord, channel, releases, gondor-v1, gitops, pull-request] tags: [corp-v1, discord, channel, releases, gondor-v1, gitops, pull-request]
related_skills: [corp-v1--main, home-v1-discord, gondor-v1-nodes, documentation-docusaurus, corp-v1--glossary] related_skills: [corp-v1-main, home-v1-discord, gondor-v1-nodes, documentation-docusaurus, corp-v1-glossary]
--- ---
# Corp v1 Releases Channel # Corp v1 Releases Channel
@@ -32,11 +32,11 @@ https://gitea.lego-cloud.eu/home-v1/gondor-v1
The skill opens a pull request for team review. Deployment must not proceed until the team approves the pull request and all required gates pass. The skill opens a pull request for team review. Deployment must not proceed until the team approves the pull request and all required gates pass.
Load the global `corp-v1--glossary` skill from `https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1--glossary` whenever project documentation needs to define or explain a reusable term. Maintain one canonical definition in the project's final top-level **Glossary** area and link to it from the owning domain page; do not duplicate glossary-style explanations across channel documentation. Load the global `corp-v1-glossary` skill from `https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1-glossary` whenever project documentation needs to define or explain a reusable term. Maintain one canonical definition in the project's final top-level **Glossary** area and link to it from the owning domain page; do not duplicate glossary-style explanations across channel documentation.
## Shared Corp v1 System Login ## Shared Corp v1 System Login
When an authorized task requires login to a Corp v1 system being built or operated, follow the shared policy in `corp-v1--main` and use only the Bitwarden-injected runtime secrets named: When an authorized task requires login to a Corp v1 system being built or operated, follow the shared policy in `corp-v1-main` and use only the Bitwarden-injected runtime secrets named:
```text ```text
HL_V1_SSO_EMAIL HL_V1_SSO_EMAIL