Skip to main content

angular-contribution

Find, prove and prepare a pull request to the angular/angular repo (framework packages, angular.dev docs in adev, docs-infra, DevTools) following Angular's own contributor docs: setup with pnpm and Bazel, running targeted tests, commit message format, coding standards, docs authoring rules, target labels and the PR template. Trigger when asked to contribute to Angular, fix an angular.dev docs error, run Angular's tests, write an Angular commit message, or prepare an Angular PR.

Source facts

Repository
erkamyaman/angular-contribution-skill
Last source activity
October 23, 2026 at 12:12
Detected SKILL.md language
English
Stars
0
Forks
0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer
8 files

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
angular-contribution
description
Find, prove and prepare a pull request to the angular/angular repo (framework packages, angular.dev docs in adev, docs-infra, DevTools) following Angular's own contributor docs: setup with pnpm and Bazel, running targeted tests, commit message format, coding standards, docs authoring rules, target labels and the PR template. Trigger when asked to contribute to Angular, fix an angular.dev docs error, run Angular's tests, write an Angular commit message, or prepare an Angular PR.
# Angular contribution Take one small, proven fix from "I found a problem" to a pull request the Angular team can merge. Everything here comes from the angular/angular repo itself. When a detail matters, re-read the live file listed in the reference, because commands and scopes change. ## First, read the repo's own agent files Before touching code in a checkout of angular/angular, read these in order: 1. `AGENTS.md` at the repo root (agent rules: pnpm, `pnpm bazel test //target`, test authoring style, use the `gh` CLI for PRs). 2. `CONTRIBUTING.md` (submission rules and contribution quality bar). 3. `contributing-docs/` (the detailed guides, listed below). 4. `.github/PULL_REQUEST_TEMPLATE.md`. 5. The repo's own agent skills under `skills/` and `.agent/` if present, for framework authoring help. ## Workflow 1. **Find.** Look for a real problem: an issue labeled `help wanted` or `good first issue`, a broken link, wrong example or typo-level docs error visible on angular.dev, or a bug hit while building an app. Search open and closed PRs first. Do not open PRs for feature requests that are not labeled `help wanted`, and discuss large changes in an issue first. See [contribution-rules.md](references/contribution-rules.md). 2. **Prove.** Reproduce before changing anything. Docs: confirm the error on the rendered page and keep the URL and a screenshot. Code: write a failing test or a minimal reproduction. See [testing.md](references/testing.md). 3. **Prepare.** Fork, sync `upstream/main`, branch, make the smallest change, format, lint, run the targeted tests, write the commit, fill the PR template. See [setup-and-build.md](references/setup-and-build.md), [commit-and-pr.md](references/commit-and-pr.md) and [branching-and-labels.md](references/branching-and-labels.md). ## Which reference to open | Task | Reference | | --- | --- | | Quality bar, CLA, what gets closed | [contribution-rules.md](references/contribution-rules.md) | | Clone, fork, install, build, run adev, dev-app | [setup-and-build.md](references/setup-and-build.md) | | Run or write tests, goldens, debugging | [testing.md](references/testing.md) | | Commit header, body, footer, PR template, fixups | [commit-and-pr.md](references/commit-and-pr.md) | | Style guide, naming, comments | [coding-standards.md](references/coding-standards.md) | | Editing angular.dev markdown or examples | [docs-authoring.md](references/docs-authoring.md) | | Which branch and `target:` label | [branching-and-labels.md](references/branching-and-labels.md) | ## Git actions Only commit, push or open the PR when the user asks for that exact action. Never add a Co-Authored-By line or any Claude attribution to commits or PR text.
View on GitHub