Concourse CI
Expert guidance for Concourse CI pipeline development, optimization, and troubleshooting. Pipeline creation, git/registry-image resources, job lifecycle hooks, YAML anchors, multi-branch pipelines with set_pipeline, oci-build-task, and gotchas like tag detection after force-push. Concourse v8.0+.
Install
Choose a supported route below. Package contents, agent registration and runtime dependencies can differ between installers.
-
Claude Code via this marketplace /plugin install concourse-ci@netresearch-claude-code-marketplaceFirst add the marketplace once in Claude Code:
/plugin marketplace add netresearch/claude-code-marketplace. Then install the selected plugin. For setup and installation scopes, seeClaude Code plugin setupA plugin can include several skills and additional components. -
npx interactive skill selection npx skills add https://github.com/netresearch/concourse-ci-skillRequires Node.js 22.20+. Run from the target project, then choose the source skills and agents in the installer. Uses the skills CLI from
skills.shInstalls skill instructions. Extra plugin hooks, commands and external runtime tools are not installed by this route. -
composer require PHP project, as a package composer require netresearch/concourse-ci-skillAllow the Composer skill installer to activate and approve skill registration when prompted. Requires
netresearch/composer-agent-skill-pluginDiscovers trusted skill packages and registers their instructions in AGENTS.md. Runtime tools may need separate setup. -
composer skills:add PHP project, direct source composer skills:add netresearch/concourse-ci-skillInstall and activate netresearch/composer-agent-skill-plugin first; approve the selected source's skill registration. Provided by
netresearch/composer-agent-skill-pluginPins source repositories without a Packagist package and records them incomposer.skills.lock. Runtime dependencies remain separate.
What you can do with it
- Pipeline Creation: Write production-ready Concourse CI pipelines with proper structure
- Resource Configuration: Configure git-resource, registry-image-resource, and 50+ resource types
- Optimization: Parallel execution, task caching, resource filtering patterns
- Troubleshooting: Debug common issues including git tag detection problems
- Best Practices: YAML anchors for DRY, job lifecycle hooks, webhook triggers
- Multi-Branch Pipelines: Dynamic pipeline management with
set_pipelineandacross - Container Builds: OCI image building with
oci-build-taskand versioning
What you get back
- Concourse pipeline and resource configuration, validation results or a diagnosis of the reported pipeline failure.
What it expects in your project
Check the source README for current examples, requirements and limitations. Open full README