security-audit
Security Audit
Overview
Security audits require systematic investigation, not surface-level checks. This skill provides a methodology for thorough security reviews with proper severity assessment, structured documentation, and security-focused ticket creation.
Core Principle: Follow the complete methodology regardless of time pressure. Cutting corners means missing vulnerabilities.
When to Use
Use when:
- Conducting security reviews or audits
- Investigating reported vulnerabilities
- Creating security documentation
- Writing security-related Jira tickets
- Assessing authentication/authorization flows
More from factorial-io/skills
himalaya
Use when working with himalaya CLI for email management - reading, composing, searching, organizing, or scripting email workflows
48drupal-recipe-content
Create Drupal recipes that import content entities (taxonomy terms, nodes, media, menu links) with multilingual translations. Use this skill whenever the user wants to create a Drupal recipe with default content, import taxonomy terms or other content entities into Drupal via recipes, set up multilingual/translated content in a recipe, or export existing content for use in a recipe. Also trigger when the user mentions "default content in recipes", "recipe with translations", or "content export for recipe".
17jujutsu
This document instructs Claude Code to use `jj` (Jujutsu) instead of `git` for version control operations. jj is a Git-compatible VCS that provides a simpler mental model and powerful history editing.
16phabalicious
Use when user mentions phab, phabalicious, deployment tasks, copying data between environments, or needs help with dev/staging/production workflows - provides command suggestions, multi-step workflows, and smart execution (read-only commands execute immediately, destructive operations require confirmation first)
15drush
Use when working with Drush CLI for Drupal site management - running cache rebuilds, config imports/exports, database queries, PHP evaluation, module management, user operations, or troubleshooting Drush commands that no longer exist
14jira-ticket-refinement
Use when the user asks to refine, update, or write a description for a Jira ticket, mentions a ticket key like CTRL-XXX, or wants to add acceptance criteria to a Jira issue
4