Multica Artifact Cicd Sync
CI/CD artifact-orchestration skill (placeholder shell): after G2 PASS and code push, call the underlying CI/CD platform skill to trigger dev/sit builds, write back to the Issue, and return the deploy URL. Parameters auto-discovered from the CI API; the orchestration layer never hardcodes parameter names. Concrete platform in the multica-platform-* layer.
Install
npx skills add it235/multica-best-practices --skill multica-artifact-cicd-syncgit clone --depth 1 https://github.com/it235/multica-best-practices.git /tmp/multica-best-practices
mkdir -p ~/.claude/skills
cp -r /tmp/multica-best-practices/templates/en_US/skills/devops/multica-artifact-cicd-sync ~/.claude/skills/multica-artifact-cicd-syncPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Artifact · CI/CD Sync (orchestration, placeholder shell) ## Purpose After G2 PASS + push, call the underlying CI/CD platform skill to trigger build/deploy. **Parameters auto-discovered from the CI API**; the orchestration layer never hardcodes parameter names. ## Agent flow ```text 1. discover-only (recommended first, check missing): python scripts/trigger_cicd.py --issue <ISSUE-KEY> --env sit --branch release/<ISSUE-KEY>-<slug> --discover-only --json 2. trigger (**only the Issue deploy branch, never a feature branch**): python scripts/trigger_cicd.py --issue <ISSUE-KEY> --env sit --branch release/<ISSUE-KEY>-<slug> --json 3. missing params: append --param name=value ``` ## Parameter resolution Default (`use_last_success=true`): 1. Read all build params of `lastSuccessfulBuild` 2. **Only** replace branch-type params (branchName / branch / gitBranch …) with `--branch` 3. `--param` may override any item; `--no-last-success` disables this --- ## Workflow A: dev deploy ```bash python scripts/trigger_cicd.py --issue <ISSUE-KEY> --env dev --service <service> --branch release/<ISSUE-KEY>-<slug> --json ``` ## Workflow B: sit deploy (G2.5 → Tester T3) ```bash python scripts/trigger_cicd.py --issue <ISSUE-KEY> --env sit --branch release/<ISSUE-KEY>-<slug> --json ``` Issue-prefix → logical-service mapping in `config.yaml` → `issue_service_map`, so `--service` is optional. ## Workflow C: multi-service
Details
- Skill name
multica-artifact-cicd-sync- Repository
- it235/multica-best-practices
- Path
templates/en_US/skills/devops/multica-artifact-cicd-sync/SKILL.md- License
- MIT
- Repo updated
- 4 November 2026
FAQ
What does the Multica Artifact Cicd Sync skill do?
CI/CD artifact-orchestration skill (placeholder shell): after G2 PASS and code push, call the underlying CI/CD platform skill to trigger dev/sit builds, write back to the Issue, and return the deploy URL. Parameters auto-discovered from the CI API; the orchestration layer never hardcodes parameter names. Concrete platform in the multica-platform-* layer.
How do I install the Multica Artifact Cicd Sync skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add it235/multica-best-practices --skill multica-artifact-cicd-sync. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Multica Artifact Cicd Sync popular?
It lives in it235/multica-best-practices, which has 279 GitHub stars and 33 forks.
Related skills
Multica Artifact Architect
279it235/multica-best-practices
Land technical design artifacts to the code repo or knowledge platform (default Git repo / Confluence). Used by @Architect to upload technical design for downstream implementation and test consumption. Swappable platform.
Multica Artifact Architect
279it235/multica-best-practices
架构师产物薄编排:校验设计草稿规范,落地时只调 multica-platform-confluence + multica-platform-jira。用于 @Architect 发布设计文档。
Multica Artifact Backend
279it235/multica-best-practices
Land API contract artifacts to the API collaboration platform (default Apifox). Used by @BackendDev to upload API contract for downstream frontend / test consumption. Swappable platform.
Multica Artifact Cicd Sync
279it235/multica-best-practices
CI/CD 产物编排:G2 PASS 且代码已 push 后调用 multica-platform-jenkins 触发 dev/sit 构建,回写 JIRA 并回传部署 URL。Python 实现,Windows / Linux 通用。
K8S Pod Rightsizer
230initializ/forge
Analyze Kubernetes workload metrics and produce policy-constrained CPU/memory rightsizing recommendations with optional patch generation and rollback-safe apply.
Multica Platform Jenkins
279it235/multica-best-practices
Platform-layer skill (placeholder shell): read/write capability for CI/CD systems (Jenkins-class) — trigger parameterized builds, poll status, fetch console logs. Parameters are auto-discovered; never hardcode. Credentials injected via runtime env. Concrete CI URL / Job list in config.yaml, never in role prompts.
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.