GitHub

GitHub builds a collaboration layer around Git. Pull requests present proposed changes for discussion and checks; issues organize work; Actions execute configured workflows; repository settings govern access and integration rules. These services are distinct from Git's local history operations. A workflow can build a container, test an API or deploy an approved artifact, but its credentials and event triggers determine what it can actually do. Competence includes the relationship between repository code, review state, automated checks and permissions, especially when contributions or model-generated changes are untrusted.

The practitioner prepares focused pull requests with meaningful context, connects work to acceptance criteria and responds to review by updating the final change. They configure checks that protect important behavior and grant automation only the access it needs. They inspect workflow triggers, dependencies and handling of sensitive configuration. Releases should identify the code and artifact that were validated. The result is a collaboration process where another engineer can review a change and understand the evidence before it enters a maintained branch or deployment.

A green check only establishes what that workflow checked. Misconfigured permissions or triggers can expose secrets or allow changes to bypass intended review. Hosted repository state does not guarantee that a deployed artifact matches the reviewed commit. Inspect access rules, workflow scope and artifact identity. GitHub skill also requires clear review communication; adding more automated checks cannot compensate for an incomprehensible or unnecessarily broad change.