--- name: git-contributions description: Develop a feature in an isolated Git worktree, make Conventional Commits and publish a concise pull request to the correct repository. Apply by default when starting feature work, continuing a feature branch, committing changes or preparing a PR; respect plan-only requests and existing contribution conventions. metadata: kind: workflow origin: local pack: sdlc domain: development phase: implementation scope: generic invocation: both role: support user-invocable: false --- # Make reviewable contributions Read [activity system](../activity-system/SKILL.md) for scope and stopping point. For writing the artifact this activity produces, read [guide-pr](../guide-pr/SKILL.md) for structure, conventions and review. Make the contribution easy to inspect and reproduce. Keep the objective's implementation, tests and documentation together in its worktree, and preserve unrelated work. Before publishing, check that the branch contains the intended change against the intended base and that the description explains the result to someone who has not read the conversation. ## Establish the target and workspace 1. Inspect the intended repository, contribution instructions, status, remotes, base and worktrees before writes. Resolve ambiguity that changes the target; preserve unrelated edits. 2. Establish one named feature worktree for the objective, fetching the intended base when available. Reuse it for implementation, tests, docs and follow-up fixes; initialize an empty repository only when needed to enable isolation. 3. Verify that actual edit/test paths are inside the objective worktree, keeping the base checkout untouched. Parallel execution, when supported and authorized, uses the objective integration branch and coordinated worktrees. If isolation is unavailable, disclose the limitation and use an agreed alternative without claiming isolation exists. ## Verify and commit 1. Use documented quality commands and the existing hook runner; [project conventions](../project-conventions/SKILL.md#establish-focused-quality-checks) owns tool setup. Verify hooks in this worktree, preserving hooksPath and partial staging. 2. Inspect formatter edits, stage intended changes, redact scan output and resolve relevant failures. Inspect the staged diff for accidental files and secrets; retain unrelated work. 3. When the contribution flow includes committing, make coherent Conventional Commits: `type(scope): concise subject`, with an optional repository-supported scope. Mark actual breaking changes and put a supplied issue reference in the repository's preferred location; otherwise omit it. CI independently repeats required checks. A contribution needs no tracker. Report local and remote state accurately. ## Publish the verified revision Inspect the intended remote/base and existing PR before publishing. Within established authorization, push the objective branch and create or update its PR; otherwise return the completed local result. Prefer Git and `gh`, with supported repository tools as an alternative. Preserve file modes and branch identity, check expected heads when available and reconcile shared history before rewriting it. For multiline descriptions, use a body file or structured tool argument. Follow fork/head conventions and repository draft/readiness rules. Commit/push authority remains separate from merging or deploying. ## Check CI after pushing After the push creates or updates the branch/PR head, check the CI/status checks for that head. A push, a green local suite or a PR link is not CI evidence. 1. Identify the check run for the pushed head; do not use a run from an earlier commit. 2. Wait for completion within the authorized scope. Report pending checks as pending; do not guess the result. 3. Inspect the failing job log, not only the summary badge. 4. Separate failures caused by the change from pre-existing, unrelated or infrastructure failures. 5. Fix failures caused by the change within the granted authority, push the fix and recheck the new head. 6. Report the actual status, failing job, cause, fix and any remaining blocked or skipped checks. Do not claim CI passed without a completed successful run. Do not disable, bypass or weaken a check to make it green. If the failure is unrelated or the fix needs authority not granted, report the exact blocker. ## Publish the reader view Create or update the PR body using the [PR contract](../artifact-system/references/contracts/pr.md) and the [quality bar](../artifact-system/references/quality-bar.md). The workflow owns isolation, commits, push and publication mechanics; the contract owns the reviewer-facing why, what changed, design impact, validation at the current head, risk, links and visibility. Before describing the PR as review-ready, apply [artifact assurance](../artifact-system/references/assurance.md) to compare the *cumulative diff* (base to current head), current-head checks, material ECR design/acceptance, actual architecture/doc changes and reviewer description. Correct authorized discrepancies or report exact blockers; the PR is a projection, not a second ECR. Before reporting completion, verify the published head, diff and required checks. Report the PR link and actual state. Keep the worktree available for review fixes until its work is safely preserved and no longer needed. ## Composition Use [artifact-system](../artifact-system/SKILL.md) for the PR reviewer view: why, actual changes, design/diagram departures, observed checks, risk and canonical ECR/issue links. Use [coordination storage](../artifact-system/references/storage/coordination.md) only to resolve verified ECR destinations. Do not publish private workspace content to public PRs.