Identify correctness, security, and spec bugs in code diffs with file-level evidence.
npx skills add https://github.com/heliohq/ship --skill review-heliohq
Please help me install this Agent Skill. Skill: review Source: https://github.com/heliohq/ship/tree/main/skills/review Command: npx skills add https://github.com/heliohq/ship --skill review-heliohq
This Skill helps you inspect a code change for real correctness, security, and spec-compliance issues before the change ships. It is designed to catch bugs that survive tests, regressions that break callers, and trust-boundary problems that need evidence-backed review.
Ask the review skill to examine the current code changes and return only concrete findings with file:line evidence.
High-intent search queries and answers about installing and using this skill.
To catch bugs in active diffs before merging, inspect staged, unstaged, and branch-level changes for correctness, security, and spec compliance using evidence-backed findings with file and line references.
Cross-file tracing detects regressions by tracking how modified shared interfaces impact callers across the repository, validating actual bugs through file-level evidence and severity ranking before code approval.
Yes, automated diff analysis supports release gating and pre-merge verification by inspecting active code changes for security regressions and data integrity issues, returning concrete findings to determine if a change safely moves forward.
The best way to perform a security audit on a branch diff is to apply evidence-based review targeting trust-boundary problems, requiring concrete file and line references, trigger conditions, and impact assessments to validate security regressions.
Yes, diff analysis works for spec compliance checking during bug triage by identifying whether active code changes violate specifications. It applies to staged, unstaged, and branch diffs, requiring file-level evidence to validate real issues before approval.
Code review requires file-level evidence for bug detection to ensure only concrete issues are reported. By demanding file and line references, trigger conditions, and impact analysis, it prevents false positives and validates real regressions before a change ships.
TokenRollAIGenerate commit messages from git diffs and project history.
tvishwanadhaCluster verified code-review findings and apply approved fixes interactively.
rsmdtValidate implementations against documented specifications with structured compliance reporting.
0x1337c0d3Identify and analyze race condition vulnerabilities in source code for TOCTOU and shared-state issues.
