From jira-orchestrator
Execute and monitor Harness pipelines with Jira integration
npx claudepluginhub markus41/claude --plugin jira-orchestratorThis skill uses the workspace's default tool permissions.
Execute and monitor Harness CI/CD pipelines with automatic Jira issue linking.
Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.
Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.
Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.
Execute and monitor Harness CI/CD pipelines with automatic Jira issue linking.
/harness-pipeline <action> [options]
Trigger a pipeline execution.
/harness-pipeline trigger --pipeline <pipeline-id> --branch <branch-name> --jira <issue-key>
Steps:
Check pipeline execution status.
/harness-pipeline status --execution <execution-id>
Returns:
Get pipeline execution logs.
/harness-pipeline logs --execution <execution-id> --stage <stage-name>
List recent pipeline executions.
/harness-pipeline list --pipeline <pipeline-id> --limit 10
When triggering a pipeline with --jira flag:
Pre-execution:
During execution:
Post-execution:
# 1. Validate the Jira issue first
/jira validate PROJ-163
# 2. Trigger pipeline with Jira link
/harness-pipeline trigger \
--pipeline my-ci-pipeline \
--branch feature/PROJ-163 \
--jira PROJ-163
# 3. Monitor execution
/harness-pipeline status --execution <returned-execution-id>
# 4. View logs if needed
/harness-pipeline logs --execution <execution-id> --stage build
This skill uses the Harness REST API (NOT MCP):
# Trigger pipeline
curl -X POST "${HARNESS_API_URL}/pipeline/api/pipeline/execute/${PIPELINE_ID}" \
-H "x-api-key: ${HARNESS_API_KEY}" \
-H "Harness-Account: ${HARNESS_ACCOUNT_ID}" \
-H "Content-Type: application/json" \
--data-urlencode "accountIdentifier=${HARNESS_ACCOUNT_ID}" \
--data-urlencode "orgIdentifier=${HARNESS_ORG_ID}" \
--data-urlencode "projectIdentifier=${HARNESS_PROJECT_ID}"
| Error | Cause | Resolution |
|---|---|---|
| 401 Unauthorized | Invalid or expired PAT | Regenerate PAT token |
| 403 Forbidden | Insufficient permissions | Check PAT scope |
| 404 Not Found | Pipeline/execution not found | Verify identifiers |
| 429 Too Many Requests | Rate limited | Wait and retry |
.env only