charlie: instructions and playbook

[shellscape]

@CharlieHelps

Please create a PR that contains an instruction set for Pull Requests following your documentation here: https://docs.charlielabs.ai/instructions-and-playbooks#authoring-instructions. The instructions should convey the following:

• Always use the Pull Request (PR) Template
• Always analyze the change to detect potentially breaking changes
• Always use conventional commit format
• If the PR contains a breaking change, use the conventional commit bang (!) symbol after the scope to indicate a breaking change, as well as annotating the PR Template appropriately
• Always use the chore(repo) type and scope in PR titles for PRs which do not contain code that affects a package source
• If a PR contains repository management tasks, even if that task affects a package's meta files, always use chore(repo) for the PR title
• Always run pnpm lint and pnpm fix:js

[charliecreates]

Expand this to see my work.

• Scoped the instruction set to the requirements in #1910 and the authoring guide.
• Added a new "Pull Request Instructions" section in CONTRIBUTING.md covering: always use the PR template, analyze for breaking changes, enforce conventional commits type(scope)!: subject, require ! for breaking PRs, use chore(repo) when code in packages isn’t affected, and always run pnpm lint/pnpm fix:js.
• Updated .github/PULL_REQUEST_TEMPLATE.md to prompt for breaking-change analysis/annotation, require a conventional-commit title (including ! when applicable), and call out chore(repo) for repository management tasks.
• Included concrete examples in CONTRIBUTING.md: feat(plugin-foo)!: drop Node 16 and chore(repo): update CI workflow to clarify scope and breaking-change notation.
• Aligned any existing commit-message wording in CONTRIBUTING.md to conventional commits and removed conflicting phrasing to avoid ambiguity around title format.
• Cross-linked the new section to the PR template (.github/PULL_REQUEST_TEMPLATE.md) and back to #1910 and the authoring guide.
• Validated impact: only CONTRIBUTING.md and .github/PULL_REQUEST_TEMPLATE.md are modified; no packages/* sources touched.
• Documented verification steps in the template to run pnpm lint and pnpm fix:js; these edits are docs/template-only, so no linter output is expected.

[charliecreates]

Opened PR #1911 with repo-scoped PR authoring instructions.

Changes

• Added .charlie/instructions/pull-requests.md with concise, always/never rules that map exactly to the issue request:

  • Always use the PR Template and fill out all sections; document migration for breaking changes.
  • Always analyze changes for potential breaking impact.
  • Always use Conventional Commits for PR titles: type(scope): summary.
  • For breaking changes, use the bang after the scope (e.g., feat(commonjs)!: …) and annotate the PR template’s breaking-change section.
  • Use chore(repo): … for PRs that don’t modify package source code and for repo management tasks, even if touching a package’s meta files.
  • Before review, run pnpm lint and pnpm fix:js.

• Included small, repo-relevant title examples to match existing conventions (e.g., fix(node-resolve): …, feat(babel): …).

PR: #1911
File: .charlie/instructions/pull-requests.md

Assignee and reviewer set to @shellscape.