Verify FP doc claims against the codebase and output a YAML audit report.
npx skills add https://github.com/tucario/Tucario-LWC-Toolkit --skill fp-doc-audit
Please help me install this Agent Skill. Skill: fp-doc-audit Source: https://github.com/tucario/Tucario-LWC-Toolkit/tree/main/.claude/skills/fp-doc-audit Command: npx skills add https://github.com/tucario/Tucario-LWC-Toolkit --skill fp-doc-audit
Verify that every justification in the project's false-positive document is grep-provable against the current codebase. This helps ensure AppExchange submissions are accurate and reviewers won't reject due to unverified claims.
Run the FP audit on the current codebase to validate all false-positive claims against the source.
High-intent search queries and answers about installing and using this skill.
Audit false-positive findings by cross-checking each justification claim against the actual codebase using grep. This process normalizes claims into verifiable statements, categorizes them as VERIFIED or STALE, and outputs a structured YAML report for reliable AppExchange submissions.
A false-positive document audit validates that every justification for a flagged security finding is grep-provable against the current codebase. It ensures static analysis claims are accurate, categorizing findings as VERIFIED, STALE FP DOC, WEAK JUSTIFICATION, or MISSING.
Run an FP doc audit to normalize each justification into verifiable statements and grep the codebase for supporting evidence. This cross-checks the actual implementation to prove the claims, ensuring reviewers will not reject the submission due to unverified statements.
Yes, you can audit false-positive docs for any Salesforce codebase. The process analyzes standard FP doc locations, normalizes claims, and greps the source code to verify evidence, generating a remediation-ready YAML report regardless of project size.
A STALE FP DOC categorization means the false-positive justification exists in the document but lacks grep-provable evidence in the current codebase. This indicates the code changed since the document was written, requiring remediation before AppExchange submission.
False-positive justifications are rejected when they are not grep-provable against the actual codebase. An FP doc audit cross-checks each claim for evidence, categorizing unsupported claims as WEAK JUSTIFICATION or MISSING to fix them before submission.
Ramprasad4121Verify suspected security bugs and produce documented TRUE POSITIVE or FALSE POSITIVE verdicts.
saddam-eng-techAudit React useEffect hooks for dependency and cleanup issues.
dreadnodeFilter low-quality and false positive vulnerability findings from scanners and agent output.
ayehiaaVerify suspected security bugs and issue TRUE POSITIVE or FALSE POSITIVE verdicts with evidence.
