Review resolved dependency versions and relevant code for security vulnerabilities. Get findings with evidence, impact, and targeted remedies, distinguishing published dependency warnings from exploit paths demonstrated in the project.
Check resolved dependencies and relevant code paths for security vulnerabilities. Use for security checks or /vuln-check; use audit for a broader correctness and maintainability assessment.
Review the instructions the agent will receive before you install.
Assess the requested security surface with evidence. A check returns findings; implement remediation when the user has requested it.
package.json and pnpm-lock.yaml for the affected dependency paths. Use current advisory data, such as pnpm audit, and record the resolved version, advisory, affected range, and verified fixed version where available. Distinguish a dependency advisory match from a demonstrated exploit path in this project.Report potential secrets only by path, line, and type, never their value or a source excerpt. Do not run automatic dependency fixes as part of a check; for requested remediation, make targeted changes and validate the affected paths.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Audit a repository or broad subsystem for security, correctness, and maintenance risks. Trace how inputs reach affected behavior, verify suspected defects, and report confirmed findings with severity, triggers, impact, and practical remedies.
Turn a reported defect into a concise bug report or issue draft that someone else can reproduce or investigate. Organize symptoms, reproduction steps, expected and actual behavior, environment, and impact while separating evidence from unknowns.
Answer questions about dsh-tui using its bundled manuals. Find relevant guidance on installation, shortcuts, configuration, themes, session migration, and VS Code integration, then cite the source file and section for checking.
Prepare and publish a pull request with a linked issue, English commit and PR titles, and a Chinese description explaining the change, implementation, and verification. Update an existing branch PR and report its URL and CI status.
Turn existing pull request review comments into prioritized next steps by checking them against the current code. Separate outstanding concerns, addressed feedback, and questions needing replies, then implement and validate fixes when requested.
Practice one programming concept through a small exercise matched to your goals, experience, and available time. Get feedback based on observable results, with hints or explained solutions and a harder variation when you are ready.