GitHub
ethics
Ethics & Compliance Officer auditing for privacy, bias, and dark patterns.
Skills IA Tests et sécurité
Découvrez les skills Tests et sécurité, comparez leurs dépôts et consultez leurs instructions.
Catégories: Tests et sécurité
Tests et sécurité Effacer les filtres
Explorer
GitHub
testing
SDET for designing test strategies and generating test cases.
GitHub
best-practices
Principal Engineer focused on maintainability, SOLID principles, and clean code.
GitHub
bugs
Senior Logic & Correctness Reviewer for finding bugs and logical flaws.
GitHub
security
Senior Security Auditor using OWASP Top 10 to identify vulnerabilities.
GitHub
code-fixer
Senior Code Fixer to apply fixes based on reviews. ONLY activates on explicit user request.
GitHub
english-lesson
Generate English lesson feedback from audio transcription
GitHub
daily-morning
デイリーノート朝用アシスタント（作成）
GitHub
meeting-minutes
音声文字起こしから議事録を生成
GitHub
monthly-review
デイリーノートからKPT形式の月次振り返りを生成（引数なしで実行月、引数ありで指定月）
GitHub
commit-msg
Generate commit message from git diff with security check
GitHub
daily-evening
デイリーノート夜用アシスタント（更新）
GitHub
pattern-enforcement
Enforce architectural patterns with ESLint rules. Block infra imports, enforce object params, prevent server/client leaks.
GitHub
storybook-journeys
Create Storybook "user journey" storyboards for React apps (page/screen stories, MSW API mocking, interaction play functions, and optional Storybook test-runner setup). Use when the user wants Storybook demos o...
GitHub
spine-framework
Evaluate and improve technical articles using the SPINE framework. Use when writing blog posts, technical documentation, tutorials, or reviewing draft articles for quality.
GitHub
create-tasks
Creates well-formed tasks following a template that engineers can implement. Use when creating tasks, defining work items, creating tasks from PRD, breaking down features, or converting requirements into action...
GitHub
research-first
Research-driven investigation. Validate solutions and explore documentation before presenting. Never ask questions you can answer yourself through research.
GitHub
documentation-standards
User-centered documentation quality framework. Eight quality dimensions, document type requirements, and review checklist. Documentation exists to serve readers, not demonstrate knowledge.
GitHub
concise-output
Enforce extreme brevity and high signal-to-noise ratio. Every word must justify its existence. Eliminates verbose explanations, filler phrases, and unnecessary elaboration.
GitHub
observability
Make functions observable with trace() wrapper, structured logging (Pino), and OpenTelemetry. Observability is orthogonal to business logic.
GitHub
branch-completion
Use when implementation is complete and tests pass. Guides completion by presenting structured options for merge, PR, or cleanup.
GitHub
structured-writing
Writing assistance with voice preservation. Structure content, ask clarifying questions, identify gaps. Small edits execute; large changes ask first.
GitHub
code-review-reception
Use when receiving code review feedback, before implementing suggestions. Requires technical verification, not performative agreement or blind implementation.
GitHub
system-architecture
Design systems for change. Trade-off analysis, ADR documentation, pattern selection. Architecture decisions must have documented rationale.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.