メニュー
Pull request conventions and requirements. Use when creating a pull request, writing a PR description, preparing changes for review, or referencing the PR template.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Project stack, module layout, and core data flow. Use when navigating the codebase, locating where functionality lives, or understanding how the client, Zustand store, and persistence layers connect.
Workflow for evaluating and resolving pull request review feedback. Use when asked to "resolve feedback" on a PR, respond to review comments, address reviewer suggestions, or work through unresolved review threads.
Commit message and branch naming conventions. Use when writing commit messages, naming branches, or squashing changes before a pull request.
MeshCore binary Companion Protocol conventions. Use when reading or writing anything in lib/meshcore/ — commands, responses, frame parsing, or transports.
TypeScript, React, and styling conventions for this project. Use when writing or reviewing any source file, adding components, or touching the state layer.
| 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"} |
The human-facing process lives in CONTRIBUTING.md
("Pull Request Process"); follow it. The points below are the agent-specific
detail.
develop (the default branch), using the
branch-naming convention in the commits skill..github/PULL_REQUEST_TEMPLATE.md.lib/meshcore/, the Description must list the affected
commands and link to the relevant
Companion Protocol docs.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.