Analyze git diffs for architecture compliance, quality, and security issues.
npx skills add https://github.com/pubky/pubky-app --skill code-review-pubky
Please help me install this Agent Skill. Skill: code-review Source: https://github.com/pubky/pubky-app/tree/main/.cursor/skills/code-review Command: npx skills add https://github.com/pubky/pubky-app --skill code-review-pubky
This Skill automates the tedious process of checking code changes against project-specific architecture rules, general quality standards, and simplification opportunities, ensuring consistent code health.
Initiate the code review process by asking the assistant to review your local uncommitted changes.
High-intent search queries and answers about installing and using this skill.
You can automate code review for uncommitted git diffs by initiating the review process, which triggers parallel sub-agents to check architecture compliance, general quality, and simplification opportunities against your project configuration files.
Architecture compliance validation in automated code quality audits is the process of verifying code changes against layer boundaries and project-specific rules defined in the repository. It operates on git diffs to ensure consistent code health and architectural integrity.
Yes, project configuration files are required to perform static analysis on source code. The review process needs access to these configurations to verify project-specific rules, detect security vulnerabilities, and provide verified, actionable feedback on maintainability.
Yes, static analysis can detect hardcoded secrets and error handling gaps during quality and security audits. The automated review process flags these vulnerabilities alongside type safety issues to ensure comprehensive code health and maintainability.
The best way to identify over-abstractions and simplification opportunities is through dedicated simplification analysis sub-agents. These agents analyze git diffs to suggest using existing project utilities, keeping the codebase clean and maintainable.
Automated multi-perspective code reviews require access to project configuration files and source code to function properly. Without proper configuration files defining project-specific rules, the review process cannot verify architecture compliance or provide verified, actionable feedback.
atholaCategorize git diffs, assess risks, and prepare release notes.
5unnykum4rAnalyze the grip codebase for performance, architecture, security, and quality issues.
RangeyRoverRun static analysis across multiple languages and generate prioritized issue reports.
thktOrchestrate AI agents to audit code quality with tiered review and static analysis.
