avoiding-false-positives

Use this skill to validate findings during a code review. For each finding, run the rejection criteria and verification checks. If a finding fails any check, drop it. In PR mode it also holds the once-per-review stacked-PR gate that decides whether completeness findings apply to the pull request at all.

Ir a la instalación Revisar archivos

Repositorio: bitwarden/ai-plugins
Última actividad en el origen: 4 de septiembre de 2026 a las 20:09
Idioma detectado de SKILL.md: inglés
Estrellas: 163
Forks: 26

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con un asistente de IA

Copia este prompt en el asistente de IA que estés usando.

Follow https://skillsmp.com/skill-install/prompt.md to install only the Agent Skill at https://github.com/bitwarden/ai-plugins/tree/main/plugins/bitwarden-code-review/skills/avoiding-false-positives.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/bitwarden/ai-plugins --skill avoiding-false-positives

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Explorador de archivos

2 archivos

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

name	avoiding-false-positives
description	Use this skill to validate findings during a code review. For each finding, run the rejection criteria and verification checks. If a finding fails any check, drop it. In PR mode it also holds the once-per-review stacked-PR gate that decides whether completeness findings apply to the pull request at all.

Volver a la búsqueda Volver a la instalación

assessing-change-risk

Rates the risk of a finished or planned code change from low to critical and says how much human review it needs and where to look. Use for "assess the risk of this change", "how risky is this PR", "how much human review does this need", "what should a reviewer look at here", or when a caller hands over a change or plan to be risk-rated. Not a code review that hunts for bugs or a security review that hunts for vulnerabilities.

2026-11-06

assessing-test-coverage

Use when determining what test coverage ALREADY exists for a specific change (a PR, Jira key, Tech Breakdown doc, Testmo CSV, changed paths, or named component), or which existing Testmo cases and tests it makes obsolete, wrong, or duplicated, including other teams' cases. Use it before writing new tests or Testmo cases. Triggers on "what's already tested", "does this PR have tests", "what coverage exists for", "is this component covered", "which behaviors have no test today", "which Testmo cases does this story make obsolete", or "which tests should be retired or updated for PM-123". A backward-looking review: it recommends update or retire, lists possible duplicates, notes other teams' affected cases, and never writes to Testmo or code. Do NOT use it to decide which new tests to add ("should I add integration tests here", "are unit tests enough"), to design a test strategy or plan, to run or fix existing tests, or to explain testing concepts like the test pyramid or which layers a repo uses.

2026-11-06

designing-test-plans

Use when designing the tests a READY Jira story or epic needs, derived from its acceptance criteria, with traceability from each criterion to its tests. Triggers on "design the tests for PM-123", "build a test plan for this epic", "what tests do these acceptance criteria need", "map tests to the acceptance criteria", "give me AC-to-test traceability for PM-123". Gates on assessing-requirement-readiness first and only designs tests for READY stories. Do NOT use it to judge readiness alone (use assessing-requirement-readiness), to choose a layer for tests you already have (use recommending-test-layers), to inventory existing tests (use assessing-test-coverage), to break work into implementation tasks or a phased work plan, including testing phases (use the bitwarden-product-analyst plugin's work-breakdown skill), or to write Gherkin manual test cases for Testmo (use writing-manual-test-cases), or to write, generate, or run automated tests in any framework or tool (for example Playwright, Selenium, Cypress, or k

2026-11-06

Ver todos los de este repositorio

avoiding-false-positives

Datos de origen

Opciones de instalación

Instalar con un asistente de IA

Revisa los archivos de origen

Más de este repositorio

Instalar con un asistente de IA

Más de este repositorio