GitHub
planning-tasks
承認済みの設計書（DESIGN.md）からTDD準拠のTODO.mdを作成します。analyzing-requirementsスキルで設計が完了・承認された後に使用します。developingスキルで実装できる形式のタスクリストを生成します。
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
managing-mcp-servers
Provides comprehensive guidance for managing MCP (Model Context Protocol) servers using the claude mcp CLI. Covers adding servers across scopes (project, local, user), transport types (stdio, sse, http), securi...
GitHub
rabbit-feedback-resolver
Process and resolve CodeRabbit automated PR review comments. Use when the user says "check rabbit review", "handle coderabbit comments", "resolve rabbit feedback", or mentions CodeRabbit PR comments. Also use a...
GitHub
sdlc
MUST BE LOADED for any coding task: implementing features, fixing bugs, writing code, refactoring, or making changes. This skill provides the mandatory step-by-step workflow for orchestrating the complete softw...
GitHub
update-description
Updates GitHub Release notes with human-readable summaries AFTER release-please creates a release. Use when user says "update release description", "improve release notes", or after merging a release-please PR....
GitHub
learn
Update fx-cc plugin agents, skills, or commands based on conversation learnings. Use when the user says "use /learn to...", "learn to...", "remember to...", "don't do X again", or when an agent/skill misbehaved...
GitHub
plugin-creator
Guide for creating effective fx/cc marketplace plugins. This skill should be used when users want to create a new Claude Code plugin (or update an existing plugin) for the fx/cc marketplace that extends Claude'...
GitHub
skill-creator
MUST BE USED when user says: 'create a skill', 'make a skill', 'new skill', 'build a skill', 'write a skill', 'add a skill', 'skill for X', or any variation. Also use when editing SKILL.md files, updating skill...
GitHub
resolve-pr-feedback
Check a PR for unresolved automated review feedback (Copilot, CodeRabbit) and invoke the appropriate resolver skills. Use when the user says "resolve PR feedback", "check PR comments", "address review comments"...
GitHub
project-management
MUST BE LOADED BEFORE modifying docs/PROJECT.md. Also load when user mentions PROJECT.md in ANY form (docs/PROJECT.md, @docs/PROJECT.md, "the project file", etc.) or discusses tasks/tracking. Triggers include:...
GitHub
copilot-feedback-resolver
Process and resolve GitHub Copilot automated PR review comments. Use when the user says "check copilot review", "handle copilot comments", "resolve copilot feedback", "address copilot suggestions", or mentions...
GitHub
agent-creator
MUST BE USED when user says 'create an agent', 'make an agent', 'new agent', 'build an agent', 'write an agent', 'add an agent', or describes agent functionality they need. Also use when editing existing agent...
GitHub
steam-linux
This skill should be used when working with Steam on Linux - managing non-Steam game shortcuts, configuring Proton/Wine compatibility, parsing VDF files, or finding Steam paths and prefixes.
GitHub
github
MUST BE USED when working with GitHub: updating PRs, editing PR descriptions/titles, creating PRs, merging, review threads, `gh` CLI commands, GitHub API, or any pull request operations. Load this skill BEFORE...
GitHub
verify-web-change
Verify web application changes work by launching the app stack and testing in a real browser. This skill should be used when the user asks to "verify the change", "test in browser", "check if it works", or afte...
GitHub
vanilla-rails-jobs
Use when writing background jobs or async operations - enforces thin job wrappers (3-5 lines) that delegate to models using _later/_now naming pattern
GitHub
vanilla-rails-testing
Use when writing Rails tests - enforces fixtures-only, integration-style controller tests, Current context setup, simple naming, and Minitest syntax
GitHub
vanilla-rails-views
Use when writing ERB templates, partials, view helpers, or Turbo Stream responses - covers partial organization, optional locals, CSS class patterns, collection rendering
GitHub
vanilla-rails-style
Use when refactoring Ruby/Rails code, organizing methods, deciding on guard clauses vs if/else, or following 37signals conventions - these patterns are counter to standard Ruby style guides
GitHub
vanilla-rails-work-breakdown
Use when planning Rails features or breaking down work into PRs - enforces 2-5 file PRs, bug fix separation, and one-sentence scope test
GitHub
vanilla-rails-controllers
Use when writing Rails controllers, adding controller actions, or implementing state changes (close, archive, publish, assign) - enforces resource extraction instead of custom actions
GitHub
vanilla-rails-models
Use when writing Rails models - enforces state-as-records not booleans, concerns as adjectives namespaced under model, invocation ordering, and private indentation
GitHub
vanilla-rails-data-modeling
Use when designing database schema, writing migrations, or making data storage decisions - enforces UUIDs, account_id multi-tenancy, state-as-records, no foreign keys, and proper index patterns
GitHub
vanilla-rails-delegated-types
Use when designing content systems where 5+ distinct types need to comingle in feeds, timelines, or searches with shared metadata and operations - NOT for simple polymorphic associations or 1-3 similar types
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é.