| name | pull-requests |
| description | Pull request conventions and requirements. Use when creating a pull request, writing a PR description, preparing changes for review, or referencing the PR template.
|
| license | Proprietary. See LICENSE for complete terms. |
| metadata | {"author":"kNoAPP","version":"1.2.0"} |
Pull Request Requirements
The human-facing process lives in CONTRIBUTING.md
("Pull Request Process"); follow it. The points below are the agent-specific
detail.
- Branch from and open the PR against
develop (the default branch), using the
branch-naming convention in the commits skill.
- Follow the PR template at
.github/PULL_REQUEST_TEMPLATE.md.
- PR titles must follow Conventional Commits and use imperative mood.
- For the "Type of Change" section, select all applicable types based on the
changes made. Do not delete the other options.
- Do not delete the comments in the PR template; replace the "None" placeholders
with appropriate content.
- If the PR touches
lib/meshcore/, the Description must list the affected
commands and link to the relevant
Companion Protocol docs.
- All five checks must pass before requesting review:
npm run spell-check,
npm run format:check, npm run lint, npm run type-check, npm run build.
@kNoAPP is requested for review automatically via CODEOWNERS — no need to
add a reviewer manually.
