skills.rest
agentculture
agentcultureOFFICIAL
Explore all skills by this author →
WebsiteGitHub

cicd

Automate Culture pull request review workflows with SonarCloud gating.

112|6|Updated Mar 19, 2026
Search Tags:#automation#code review#pull request#github actions#ci-cd#sonarcloud#thread resolution
One-click install
npx skills add https://github.com/agentculture/culture --skill cicd-agentculture
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cicd
Source: https://github.com/agentculture/culture/tree/main/.claude/skills/cicd
Command: npx skills add https://github.com/agentculture/culture --skill cicd-agentculture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires agex, gh, jq, bash, python3, curl, git, uv, and includes scripts (resource) components.

What problem does it solve?

CI/CD review cycles for Culture PRs are slow and error-prone when you manually create PRs, poll for reviewer readiness, triage inline threads, and re-check SonarCloud gates before declaring the PR ready.

Core Features & Use Cases

  • Full PR lifecycle lane: create a PR, wait for the initial briefing, poll again when needed, and then guide the triage loop (fix or push back) until all review threads are resolved.
  • Culture-specific gating extensions: run a SonarCloud + issues + hotspots + unresolved-inline-thread status check, and an await flow that fails fast on Sonar ERROR or remaining unresolved threads.
  • PR comment workflow with consistent signing: reply to review comments in bulk (JSONL) or single-shot while ensuring the repo-configured Claude signature is applied consistently.

Use cases:

  • You just pushed a branch and want a structured “wake me when it’s review-ready” flow, including SonarCloud error/unresolved-thread gating.
  • You received review comments and need a deterministic loop to decide FIX vs PUSHBACK, make changes, and resolve threads before preparing the PR for merge.
  • You must address portability and project-convention issues detected during PR review.

Quick Start

Ask your assistant to run the Culture cicd skill to create a PR for your current branch, wait for the reviewer briefing, then gate on SonarCloud ERROR and unresolved threads before you declare the PR ready for merge.

Frequently Asked Questions about cicd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub pull request reviews with SonarCloud gating?▼

Automate GitHub pull request reviews with SonarCloud gating by creating a PR lifecycle flow that polls for reviewer readiness, triages inline threads, and enforces SonarCloud ERROR checks before merge readiness. This ensures all unresolved threads are consistently resolved.

What is the best way to wait for reviewer readiness on a pull request?▼

The best way to wait for reviewer readiness on a pull request is running an await flow that polls for the initial reviewer briefing and fails fast on SonarCloud errors or remaining unresolved inline threads, ensuring the PR is fully vetted before proceeding.

How do I resolve inline review threads on a pull request in bulk?▼

Resolve inline review threads on a pull request in bulk by processing review comments through a JSONL workflow that applies a consistent repo-configured signature, allowing you to reply to multiple threads simultaneously while maintaining project conventions.

Can I enforce SonarCloud error checks before merging a pull request?▼

You can enforce SonarCloud error checks before merging a pull request by applying a status check that evaluates issues, hotspots, and unresolved inline threads, failing the merge readiness flow if SonarCloud errors or unresolved threads are detected.

How do I triage pull request review comments deterministically?▼

Triage pull request review comments deterministically by running a structured loop that decides between FIX or PUSHBACK actions for each thread, implements the changes, and resolves the threads before preparing the pull request for SonarCloud gated merge.

Do I need specific dependencies to run SonarCloud gated pull request workflows?▼

Running SonarCloud gated pull request workflows requires dependencies including agex, gh, jq, bash, python3, curl, git, and uv to manage branch flows, execute lifecycle verbs, and process status reporting for consistent merge readiness checks.

Related Skills

Explore More Software Engineering Skills→
brainbrewlabsbrainbrewlabs
7

git

Coordinates Git commit, push, and PR actions via git-manager modes.

Official
Intermediate
LaPaGaYoLaPaGaYo

deploy

Automate end-to-end deployment workflows with health checks and release gating.

Community
Advanced
diegoknskdiegoknsk

sonarcloud-dotnet

Integrate .NET projects with SonarCloud via GitHub Actions for static analysis and coverage.

Community
Advanced
nashgaonashgao
3

Pull Request Workflow

Manage pull request lifecycle with validation, review tracking, and merging.

Community
Advanced