Scan pull requests for repository hygiene and compliance issues.
npx skills add https://github.com/AIAsys/AIASys --skill pr-check-aiasys
Please help me install this Agent Skill. Skill: pr-check Source: https://github.com/AIAsys/AIASys/tree/main/.team-skills/pr-check Command: npx skills add https://github.com/AIAsys/AIASys --skill pr-check-aiasys
Contributors to the AIASys project often miss critical repository hygiene and compliance issues when submitting or merging pull requests, leading to security risks, bloated code history, broken builds, and inconsistent project standards that require time-consuming cleanup later.
Use the pr-check skill to run all required pre-merge quality checks on your current feature branch before opening or merging a pull request.
High-intent search queries and answers about installing and using this skill.
You can automate pull request quality checks by scanning your feature branch for gitignore violations, leaked sensitive files, merge conflict markers, and non-compliant commit messages before submission. This prevents security risks and broken builds from entering the codebase.
Scanning a git repository for hygiene issues involves checking for oversized binary files, temporary debug artifacts, and unresolved merge conflict markers. Running these checks locally catches required issues upfront, reducing review cycles and avoiding CI failures.
Yes, pre-merge validation enforces project-specific requirements including changelog updates for user-facing changes and version number consistency for release PRs. This maintains codebase standards and prevents incomplete feature submissions.
Validating commit messages and skill registration completeness requires checking commits against project-specific compliance rules. This ensures new or modified skills are fully registered and commit messages meet the required standards before merging.
Yes, you can run pre-submission checks locally to catch leftover debug artifacts and temporary files. This comprehensive PR scanning identifies easily preventable mistakes before opening a pull request, avoiding time-consuming cleanup later.
If your pull request contains leaked sensitive files or gitignore violations, automated pre-merge validation will flag them. This prevents security risks and bloated code history by catching these repository hygiene issues before they are merged.
gajjalaashok75-UIStages modified files, commits conventionally, and pushes to remote tracking repository.
Conceptual-MachinesCreate and push a v-prefixed git tag on the main branch.
hidonguyenExecute unit, integration, e2e, and UI tests across JavaScript/TypeScript, Python, Go, Rust, and Flutter projects.
kid-sidEnforce conventional commits, branch naming, and safe force-push rules in Git workflows.
