An 800-line PR is likely too large to review effectively. Split it into smaller, independently understandable logical changes, keeping each PR preferably below 300 changed lines where practical. Separate refactors, formatting-only changes, behavior changes, tests, and documentation when they do not need to be reviewed together. Before splitting, self-review the diff and identify dependencies. Create focused branches with the appropriate prefix, such as `refactor/...`, `feat/...`, or `fix/...`...
Scanned 9/5/2026
Install to Claude Code
Skills Directorynpx -y skills add HoangNguyen0403/agent-skills-standard --skill common-git-collaboration --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Common Git Collaboration?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/hoangnguyen0403-common-git-collaboration-e7eb7348)More formats (shields.io, HTML) on the badges page.
An 800-line PR is likely too large to review effectively. Split it into smaller, independently understandable logical changes, keeping each PR preferably below 300 changed lines where practical. Separate refactors, formatting-only changes, behavior changes, tests, and documentation when they do not need to be reviewed together.
Before splitting, self-review the diff and identify dependencies. Create focused branches with the appropriate prefix, such as `refactor/...`, `feat/...`, or `fix/...`; order the pull requests if one depends on another. Each PR should explain what changed, why, how it was tested, and any issue link. Keep each commit focused and use Conventional Commit messages. Rebase a feature branch when needed to maintain a clean linear history, then ensure linting, tests, and builds pass before requesting merge.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.
Official Google SEO guide covering search optimization, best practices, Search Console, crawling, indexing, and improving website search visibility based on official Google documentation
SEO optimization with keyword analysis, readability assessment, technical validation, content quality. Use for search rankings, blog posts, content audits, or encountering keyword density, readability scores, meta tags, schema markup errors.
Python backend development expertise for FastAPI, security patterns, database operations, Upstash integrations, and code quality. Use when: (1) Building REST APIs with FastAPI, (2) Implementing JWT/OAuth2 authentication, (3) Setting up SQLAlchemy/async databases, (4) Integrating Redis/Upstash caching, (5) Refactoring AI-generated Python code (deslopification), (6) Designing API patterns, or (7) Optimizing backend performance.
PTES-aligned adversarial security audit for backend, frontend, and mobile applications. Produces a CVSS-scored Hacker Report with verified PoCs and phased remediation.
