Multica Platform Jenkins

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.

279 stars 33 forksDevOps & Cloud

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add it235/multica-best-practices --skill multica-platform-jenkins
Manual install
git 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/platform/multica-platform-jenkins ~/.claude/skills/multica-platform-jenkins

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Platform · Jenkins (placeholder shell)

> This is a **platform-layer placeholder shell**. The public multica-best-practices binds to no specific company's internal URLs or credentials.
> To onboard your own CI/CD system, only edit this skill's `config.yaml` and `scripts/`; all upstream orchestration skills stay untouched.

## Purpose

CI/CD system **read + write**: trigger Jobs, poll builds, fetch `consoleText`, return build URLs.

> **Parameter auto-discovery**: connect to the CI system API to read each Job's required parameters; Agents must not hardcode parameter names.

Default CI URL configured in `config.yaml` → `cicd.base_url` (placeholder: `http://<your-cicd-host>`).

## Agent standard flow (required)

```text
1. Resolve service (jobs-catalog / issue_service_map) + **deploy branch** (from the Issue source + affected ends, not feature; for linked Issues use the branch in the external system)
2. discover (required) — default copy from lastSuccessfulBuild, only override deploy branch
3. ready=false → fill missing params or BLOCKED ask human
4. trigger: multica-artifact-cicd-sync → trigger script
```

**Parameter priority**: `--param` > **branch hint** (branchName etc.) > **last SUCCESS build params** > CI default

## Files (suggested structure)
Read the full skill on GitHub

Details

Skill name
multica-platform-jenkins
Path
templates/en_US/skills/platform/multica-platform-jenkins/SKILL.md
License
MIT
Repo updated
4 November 2026

FAQ

What does the Multica Platform Jenkins skill do?

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.

How do I install the Multica Platform Jenkins skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add it235/multica-best-practices --skill multica-platform-jenkins. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Multica Platform Jenkins popular?

It lives in it235/multica-best-practices, which has 279 GitHub stars and 33 forks.

Related skills

Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.