Detect suspicious patterns and anomalies across a codebase.
npx skills add https://github.com/JimmyTranDev/dotfiles --skill code-soundness
Please help me install this Agent Skill. Skill: code-soundness Source: https://github.com/JimmyTranDev/dotfiles/tree/main/src/opencode/skills/code-soundness Command: npx skills add https://github.com/JimmyTranDev/dotfiles --skill code-soundness
Detects suspicious patterns, anomalies, inconsistencies, and accidental behavior that undermine code quality across a codebase, enabling faster discovery and remediation.
Run an automated scan of the repository to surface code smells and generate a prioritized report
High-intent search queries and answers about installing and using this skill.
To detect code smells across a multi-language repository, run an automated scan to identify suspicious patterns, anomalies, and inconsistencies, generating a structured report detailing findings, risk levels, and recommended remediations.
The best way to surface inconsistent naming and vestigial constructs during code reviews is to apply pattern analysis, which highlights duplicated logic and questionable patterns to produce review-ready, prioritized reports for faster triage.
Yes, you can use static analysis to find silent failures and unintended code paths. Anomaly detection identifies unusual behavior and misaligned intent across modules, enabling faster discovery and remediation of accidental issues.
Code soundness analysis works effectively for maintenance on large existing codebases by applying automated scans to surface questionable patterns and inconsistencies, helping developers discover and remediate underlying issues efficiently.
Automated code review report generation helps with triaging anomalies by producing structured, review-ready findings aligned with developer workflows. This structured output details risk levels and recommended remediations, accelerating the triage process.
JeromyJSmithInitialize Graphify code graph analysis for the LATTICE repository.
aist-ai-sastGroup SAST findings by group_name and project path prefix into Jira tickets.
benediktmsCheck code against project linter conventions for naming, formatting, and structure.
aarushlohitReview pull request changes for correctness, security, performance, and quality.
