CC-39773: bugfixer skill

[vitaliiivanovspryker]

PR Description

CC-39773 — AI Dev SDK: Autonomous Bugfixer Claude Plugin
Ticket: https://spryker.atlassian.net/browse/CC-39773

Adds the spryker-bugfix skill to the plugin (skills/spryker-bugfix/): an end-to-end, orchestrated bug-fixing workflow for Spryker projects. It is a pure orchestrator — it runs a fixed sequence of stages (Steps 0–12) and delegates the heavy work of each stage to skills/agents already installed in the plugin, carrying compact state between them and enforcing a verification loop.

Workflow spine: reproduce → root-cause → minimal fix → functional tests → static validation → code review → independent QA → final verification → (autonomous) commit + push + Draft PR + remote-CI watch.

Highlights

• Two modes — Collaborative (stops at decision points and before push) and Autonomous (runs unattended to a pushed Draft PR + ~15-min CI watch loop; every fork is a logged CRITICAL DECISION, not a question).
• Ticket-optional intake — bug context can come from any tracker ticket (JIRA, GitHub Issues, …) or a plain description; a ticket is never required (no-ticket fallbacks for branch/commit/PR title).
• Claude-only orchestration — every stage delegates to an installed Skill() or Claude subagent; no third-party MCP is required for the core flow (the only external touchpoint is the optional Step 0 ticket pull).
• Run-lean context discipline — bulk output (Chrome, XDebug, Codeception, phpcs/phpstan, review, verification, CI logs) runs in subagents that write raw logs to a per-run cache dir and return only compact verdicts; the orchestrator keeps a small State Object.
• Plan tracking — the 12 stages are arranged as a TaskCreate/TaskUpdate/TaskList task list that survives compaction and scheduled wake-ups, alongside the run log and decision log.
• Verification loop — Steps 8 (review), 9 (QA), 10 (final verification) and 11 (remote CI) are gates sharing one attempt counter that loops back to root-cause; hard stop at attempt > 3.
• Static validation delegates to static-validation; the final gate is an end-to-end final verification in the running app (spryker-verifier / spryker-runtime) rather than a local-CI run.

Files (skills/spryker-bugfix/): SKILL.md (workflow spine), stages.md (per-step instructions + stage→skill quick map), reference.md (run-lean discipline, principles, decision log, red flags), README.md (overview + a Mermaid flow diagram).

Related

• Docs PR: CC-39773: Document spryker-bugfix skill in AI Dev SDK docs spryker/spryker-docs#3813
• Ticket: https://spryker.atlassian.net/browse/CC-39773

Steps before you submit a PR

• Please add tests for the code you add if it's possible.
• Please check out our contribution guide: https://docs.spryker.com/docs/dg/dev/code-contribution-guide.html
• Add a contribution-license-agreement.txt file with the following content:
  I hereby agree to Spryker's Contribution License Agreement in https://github.com/spryker/incremental-installer/blob/HASH_OF_COMMIT_YOU_ARE_BASING_YOUR_BRANCH_FROM_MASTER_BRANCH/CONTRIBUTING.md.

This is a mandatory step to make sure you are aware of the license agreement and agree to it. HASH_OF_COMMIT_YOU_ARE_BASING_YOUR_BRANCH_FROM_MASTER_BRANCH is a hash of the commit you are basing your branch from the master branch. You can take it from commits list of master branch before you submit a PR.

Checklist

• I agree with the Code Contribution License Agreement in CONTRIBUTING.md