원클릭으로
phpunit-test-reconciling
Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use this skill when the user asks to write, create, draft, or validate an Architecture Decision Record for the Shopware core repository — phrases like "write an ADR", "create an architecture decision record", "draft a decision record", "validate this ADR", "check ADR quality", or when they mention "ADR", "architecture decision record", or "decision record" in a context that calls for capturing or auditing an architectural decision. Interactively creates ADRs (simple or multi-domain structure) with proper YAML front matter and guided content, and validates existing ADRs against front matter rules, required coverage, structure, writing style, and Shopware-specific patterns.
Use this skill when the user explicitly asks to generate, write, draft, or create a commit message, squash commit, commit title, or merge commit message for the Shopware core repository (shopware/shopware). Supports two modes — full commit messages (title + body) for branch commits, and squash merge titles (title-only) for trunk merges — the skill auto-detects which based on the current branch and PR target. Analyzes diffs, infers scope from Shopware's directory structure, and detects breaking changes. Do NOT activate during implementation work or when the user is still writing code; only when they are ready to capture a finished change. For commit messages in the ai-coding-tools marketplace repo itself, use the commit-message-generating skill instead.
Use this skill when the user asks to write, draft, create, or improve a PR description for a Shopware core repository PR — AND that PR targets a non-trunk feature branch (not trunk itself). Trigger phrases like "write a PR description", "draft the PR", "what should I put in the PR body". The skill detects the target branch and only activates for non-trunk targets; for trunk-targeting PRs, use pr-description-writing instead. Do NOT activate mid-implementation — only when the user is ready to describe finished changes. Produces a conventional-commit title and a narrative-prose description with topical subsections, leveraging the diff against the target branch and any related PRs in the chain.
Use this skill when the user asks to write, draft, create, or improve a PR description, is about to create a PR, or mentions "PR description", "pull request description", or "PR template" — AND that PR targets trunk in the Shopware core repository (shopware/shopware). The skill detects the target and only activates for trunk-targeting PRs; for PRs targeting a feature branch, use feature-branch-pr-writing instead. Do NOT activate mid-implementation — only when the user is ready to describe finished changes. Produces a conventional-commit title and a description following Shopware's 5-section template, leveraging the full branch diff against trunk and session context.
Use this skill when the user is completing features, deprecations, or breaking changes in the Shopware core repository that affect external developers, or when they ask to write release info, upgrade entries, release notes, release documentation, or changelog entries — phrases like "write a release info entry for my changes", "add an upgrade note", "what goes in RELEASE_INFO", "draft an UPGRADE.md entry". Drafts entries for RELEASE_INFO-6.*.md and UPGRADE-6.*.md based on the full branch diff against trunk, calibrated to the magnitude of change. Do NOT activate mid-implementation, for internal refactoring, non-critical bug fixes, or test-only changes — those do not get release entries.
Use this skill when the user just installed the chunkhound-integration plugin and needs to configure it, asks how to set up semantic code search or ChunkHound — phrases like "help me set up chunkhound", "configure semantic search", "set up code research" — or when ChunkHound MCP tools fail with config or connection errors. Walks through prerequisite checks (chunkhound CLI, embedding provider — VoyageAI or OpenAI), creates .chunkhound.json with the chosen provider, runs the initial index, and validates the MCP server connection.
| name | phpunit-test-reconciling |
| version | 4.2.2 |
| description | Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent. |
| user-invocable | false |
| allowed-tools | Read, Glob, Grep, mcp__plugin_test-writing_test-rules__get_rules |
Re-evaluate review findings against incoming critique and emit a binding revised stance, for any test type (unit, integration, or migration). Run in one of two modes: peer (reconcile against co-reviewers' findings) or adversary (reconcile against adversary challenges). Evidence — the rule's detection algorithm applied to the code — decides every disposition.
digraph reconcile {
"Reconcile request" [shape=doublecircle];
"mode?" [shape=diamond];
"peer: load own + peer findings on shared files" [shape=box];
"adversary: load own stance + adversary challenges" [shape=box];
"Per contested finding: load detection algorithm (inline RULES block by ID if rules set, else get_rules), apply to code" [shape=box];
"Evidence decides disposition — never social pressure" [shape=box];
"Emit binding revised stance" [shape=doublecircle];
"Reconcile request" -> "mode?";
"mode?" -> "peer: load own + peer findings on shared files" [label="peer"];
"mode?" -> "adversary: load own stance + adversary challenges" [label="adversary"];
"peer: load own + peer findings on shared files" -> "Per contested finding: load detection algorithm (inline RULES block by ID if rules set, else get_rules), apply to code";
"adversary: load own stance + adversary challenges" -> "Per contested finding: load detection algorithm (inline RULES block by ID if rules set, else get_rules), apply to code";
"Per contested finding: load detection algorithm (inline RULES block by ID if rules set, else get_rules), apply to code" -> "Evidence decides disposition — never social pressure";
"Evidence decides disposition — never social pressure" -> "Emit binding revised stance";
}
The spawn prompt provides:
mode — peer or adversaryscope per file — list of method names, or full class. Reconcile only findings within the scoped methods; discard incoming items targeting out-of-scope code.{rules} (optional) — the pre-rendered rule catalog as text, provided in your prompt. When set, find contested rules by ID in that text; it holds every rule, so NEVER read, open, search, or locate a rule file by any means — no Read/Grep/Glob, no get_rules — not even to resolve a missing ID. Reading the cited code is unaffected. When omitted, rules load via get_rules.Mode peer additionally provides:
own_findings — your findings from the prior wave, per filepeer_findings — co-reviewers' findings on the same files, per fileMode adversary additionally provides:
own_stance — your current binding stance, per fileadversary_challenges — challenges to consensus, resurrections, adversary-introduced findings, and endorsements, per fileLoad references/reconciliation-rules.md. Apply it to every disposition in both modes.
For each finding under contention:
{rules} is set, find the rule by ID in that inline text; otherwise call mcp__plugin_test-writing_test-rules__get_rules(ids={rule_id}).Compare own findings against peer findings per file:
Output binding stance per file: findings you stand by, and withdrawn with reasons. See references/output-format.md.
Evaluate every adversary item per file:
Output binding stance per file with an adversary_impact tag on every entry: findings (defended | unchanged), re_adopted (resurrected), withdrawn (overturned), adopted_new (introduced). See references/output-format.md.
If mcp__plugin_test-writing_test-rules__get_rules is unavailable, detection algorithms cannot be verified.
peer: concede peer findings you cannot verify; note the limitation in the stance.adversary: maintain your current positions; note the limitation in the stance.