skills.rest
peanutDD
peanutDDCOMMUNITY
Explore all skills by this author →
GitHub

project-code-review-author

Prepare code review submissions with pre-submit checks and PR description structure.

1|Updated Jan 24, 2026
Search Tags:#coding-standards#code-review#pull-request#continuous-integration#review-feedback#pr-descriptions#contributing-guide
One-click install
npx skills add https://github.com/peanutDD/upload-download-util --skill project-code-review-author
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-code-review-author
Source: https://github.com/peanutDD/upload-download-util/tree/main/.trae/skills/project-code-review-author
Command: npx skills add https://github.com/peanutDD/upload-download-util --skill project-code-review-author

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides authors to prepare and respond to code reviews within the repository, ensuring PR submissions are clear, complete, and aligned with project guidelines.

Core Features & Use Cases

  • Pre-submit preparation: read CONTRIBUTING and CODE_REVIEW_GUIDE, confirm scope, and run local checks (backend: cargo fmt / clippy / test; frontend: lint / test / build).
  • PR description template: include change purpose, review category, CI status, and hotfix notes when applicable.
  • Self-check and response: structured guidance for addressing feedback with traceable replies and re-submission.

Quick Start

Follow this guide before submitting a PR to ensure a complete description and clear review context.

Frequently Asked Questions about project-code-review-author

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a pull request description for code review?▼

To write a pull request description for code review, include the change purpose, review category, CI status, and hotfix notes to provide clear and complete context for reviewers.

What pre-submit checks should I run before a pull request?▼

Pre-submit checks for a pull request involve reading CONTRIBUTING guidelines, confirming scope, and running local checks like cargo fmt, clippy, test for backend or lint, test, build for frontend.

How do I address review feedback on my pull request?▼

To address review feedback on your pull request, provide traceable replies to comments, complete the self-check list, and ensure re-submission aligns with project guidelines.

Does this code review preparation work for both frontend and backend changes?▼

Yes, code review preparation applies to both frontend and backend changes, codifying pre-submit checks, PR description structure, and CI status notes across both domains.

What is a structured self-check list for code review submissions?▼

A structured self-check list for code review submissions is a pre-submit verification mechanism that ensures your PR aligns with project guidelines, confirms scope, and validates local test status.

Related Skills

Explore More Software Engineering Skills→
vanyastaffvanyastaff
2

aif-verify

Validate Rust code against the Nebula project's CI gate sequence.

Community
Basic
Nairon-AINairon-AI
7

flux-autofix

Automates cloud-based PR fixes for CI failures and reviewer feedback via GitHub.

Official
Advanced
flatrickflatrick
1

django-verification

Automate Django project verification with linters, tests, and security scans.

Community
Advanced
carlopezzutocarlopezzuto
3

code-review-excellence

Structure pull request reviews with phase-based checklists and feedback templates.

Community
Advanced