Skip to content

Add ACS patch release workflow#1

Open
davdhacs wants to merge 2 commits intomainfrom
add-patch-release-workflow
Open

Add ACS patch release workflow#1
davdhacs wants to merge 2 commits intomainfrom
add-patch-release-workflow

Conversation

@davdhacs
Copy link
Copy Markdown

Summary

  • Adds patch-release/ directory as a thin ACP workflow wrapper
  • Loads the patch-release skill from the internal stackrox/skills repo at runtime
  • System prompt covers only ACP-specific credential handling (workspace secrets, MCP Jira, token expiry)
  • All procedures, decision frameworks, and reference data live in stackrox/skills (PR: https://github.com/stackrox/skills/pull/5)

Files

  • patch-release/.ambient/ambient.json — ACP workflow config with slim system prompt
  • patch-release/.claude/commands/patch-release.md — Loader that clones skills repo and delegates to SKILL.md
  • patch-release/CLAUDE.md — Architecture and testing docs
  • CLAUDE.md — Updated to list both workflows

Architecture

ambient-workflows (public)          stackrox/skills (internal)
├── patch-release/                  └── plugins/patch-release/
│   ├── .ambient/ambient.json           ├── skills/patch-release/SKILL.md
│   ├── .claude/commands/               ├── reference/*.md
│   │   └── patch-release.md            └── scripts/acs-operator-test.sh
│   └── CLAUDE.md

The /patch-release command locates or clones the skills repo, then follows the SKILL.md process. Works from both ACP and local Claude Code.

Test plan

  • Load in ACP with "Custom Workflow", path patch-release
  • Verify /patch-release 4.8.11 clones skills repo and presents status
  • Verify credential detection works (MCP Jira in ACP, curl fallback locally)
  • Depends on: https://github.com/stackrox/skills/pull/5

🤖 Generated with Claude Code

janisz and others added 2 commits April 27, 2026 13:24
HIGH PRIORITY fixes from /simplify review:

- Create reference/teams.md: Canonical team list with responsibilities
- Create reference/constants.md: All hardcoded values (JIRA filters, confidence thresholds, frequency thresholds, severity thresholds, output paths, etc.)
- Update all reference/*.md files to point to teams.md and constants.md instead of duplicating content
- Remove duplicate team lists from CODEOWNERS-patterns.md, team-mappings.md, error-signatures.md, vulnerability-decision-tree.md, flaky-test-patterns.md

MEDIUM PRIORITY fixes:
- Remove "Usage in Triage" sections from reference files (implementation details belong in command files, not reference docs)
- Remove meta-commentary from README.md ("Future Enhancement", "Why READ-ONLY" justifications)
- Replace duplicate confidence tables in FIELD_REFERENCE.md with reference to constants.md
- Shorten 58-line JSON example in FIELD_REFERENCE.md to concise structure
- Update CLAUDE.md to reference canonical sources instead of duplicating team lists and confidence scores

Result:
- Single source of truth for teams, confidence thresholds, and constants
- Reference files are now lookup tables, not implementation guides
- Documentation references canonical sources to prevent drift

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Adds patch-release/ directory as an ACP workflow wrapper that loads
the patch-release skill from the internal stackrox/skills repo.

The wrapper provides:
- ambient.json with system prompt (phase model, state detection,
  decision frameworks, credential handling, error recovery)
- /patch-release command that locates/clones the skills repo
- CLAUDE.md documenting the architecture

The actual procedures, reference data, and scripts live in
stackrox/skills (internal) so they work from both ACP and local
Claude Code. The workflow is stateless — it detects progress from
external signals (git tags, milestones, Jira, Konflux, PRs) so
any engineer can pick up a release at any point.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@davdhacs davdhacs requested a review from janisz April 28, 2026 04:54
@davdhacs davdhacs marked this pull request as ready for review April 28, 2026 04:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants