For severity classes, enterprise profile behavior, and false-positive guidance, see Rules.
The package exposes these SymPress custom sniffs:
SymPress.Arrays.ArrayDoubleArrowAlignmentSymPress.Arrays.MultiLineArraySymPress.Classes.AccessorNamingSymPress.Classes.DeprecatedSerializableInterfaceSymPress.Classes.DeprecatedSerializeMagicMethodSymPress.Classes.ClassLengthSymPress.Classes.PropertyLimitSymPress.Complexity.NestingLevelSymPress.ControlStructures.AlternativeSyntaxSymPress.ControlStructures.DisallowElseSymPress.Encoding.Utf8EncodingCommentSymPress.Files.FileLengthSymPress.Files.LineLengthSymPress.Formatting.AlphabeticalUseStatementsSymPress.Formatting.TrailingSemicolonSymPress.Formatting.UnnecessaryNamespaceUsageSymPress.Functions.ArgumentTypeDeclarationSymPress.Functions.DisallowCallUserFuncSymPress.Functions.DisallowGlobalFunctionSymPress.Functions.FunctionBodyStartSymPress.Functions.FunctionLengthSymPress.Functions.ReturnTypeDeclarationSymPress.Functions.StaticClosureSymPress.Namespaces.Psr4SymPress.NamingConventions.ElementNameMinimalLengthSymPress.NamingConventions.VariableNameSymPress.PHP.DisallowShortOpenTagSymPress.PHP.DisallowTopLevelDefineSymPress.PHP.ShortOpenTagWithEchoSymPress.Strings.VariableInDoubleQuotesSymPress.Usage.IsNullSymPress.Variables.RedundantAssignmentSymPress.WhiteSpace.ConstantSpacingSymPress.WhiteSpace.MultipleEmptyLinesSymPress.WordPress.HookClosureReturnSymPress.WordPress.HookPriority
Run phpcs -e --standard=SymPress to see the active custom sniff list resolved by the installed package.
The profile retains WPCS WordPress.DB.PreparedSQL and
WordPress.DB.PreparedSQLPlaceholders. WPCS 3.1 identifies receivers by tokens
named $wpdb or wpdb; a property literally called wpdb can be covered,
but typed $this->db, aliases, factory results and differently named parameters
are not reliably covered. Consumers must also include the WordPress PHPStan
profile from sympress/qa, which registers the receiver-type based
sympress.preparedSql rule. This complementary check is not a custom PHPCS sniff
and does not change the pure PHP profile. Audited raw SQL boundaries require a
narrow documented exception and regression tests.