تشغيل أي مهارة في Manus بنقرة واحدة

pull-requests

النجوم٤

التفرعات٠

آخر تحديث٢٥ يونيو ٢٠٢٦ في ٢٣:٢١

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 ويثبّتها لك.

تشغيل في Manus

المصدر

kNoAPP

kNoAPP/MeshCore-WebAgent

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

SKILL.md

readonly

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.

المزيد من هذا المستودع

نفس المستودع

architecture

kNoAPP/MeshCore-WebAgent

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.

2026-07-054

resolving-review-feedback

kNoAPP/MeshCore-WebAgent

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.

2026-06-294

commits

kNoAPP/MeshCore-WebAgent

Commit message and branch naming conventions. Use when writing commit messages, naming branches, or squashing changes before a pull request.

2026-06-254

protocol

kNoAPP/MeshCore-WebAgent

MeshCore binary Companion Protocol conventions. Use when reading or writing anything in lib/meshcore/ — commands, responses, frame parsing, or transports.

2026-06-254

code-style

kNoAPP/MeshCore-WebAgent

TypeScript, React, and styling conventions for this project. Use when writing or reviewing any source file, adding components, or touching the state layer.

2026-06-174

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.