phpcs-check-fix

Fix PHP coding style issues using PHPCS and PHPCBF. Use this skill whenever the user mentions PHPCS, code style, coding standard, cs:fix, cs:check, PHP formatting, or asks to fix/check PHP code style. Also activate when you notice PHP files have been modified and need style compliance, or when a CI PHPCS check has failed.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An excellent, tightly-written procedural skill: concrete commands, copy-paste code, explicit thresholds, a sequenced workflow with a re-check feedback loop, and clean section organization. It respects Claude's intelligence while remaining fully actionable.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, skipping basic explanations of PHPCS or PHP concepts, with every section and concrete threshold (complexity 7/10, line length 160/200) earning its place.	3 / 3
Actionability	It provides fully executable commands (composer cs:fix, composer cs:check, vendor/bin/phpcs --standard=phpcs.xml path/to/File.php) and copy-paste-ready code examples for ignore directives and type hints.	3 / 3
Workflow Clarity	The four-step 'exact sequence' includes an explicit validation feedback loop (step 4 re-runs cs:check and instructs fixing any new issues), giving clear sequencing with error-recovery checkpoints.	3 / 3
Progressive Disclosure	As a single-purpose skill with no bundle files, it is well-organized into clear sections (Commands, Workflow, Handling Issues, Scoping, CI), which satisfies progressive disclosure for a simple skill without external references.	3 / 3
	Total	12 / 12 Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description with explicit 'what' and 'when' guidance and rich, natural trigger terms. It is slightly less comprehensive on the breadth of concrete actions, but otherwise well-scoped and distinct.

Suggestions

Consider briefly enumerating a few more concrete actions (e.g., 'detect violations, auto-fix mechanical issues, and document exceptions') to push specificity from comprehensive actions rather than a single fix/check loop.

Dimension	Reasoning	Score
Specificity	Names the concrete tools (PHPCS, PHPCBF) and the core action (fix PHP coding style issues), but does not enumerate multiple distinct concrete actions beyond fix/check, so it is not fully comprehensive.	2 / 3
Completeness	It explicitly states what it does ('Fix PHP coding style issues using PHPCS and PHPCBF') and provides explicit 'Use this skill whenever...' triggers answering when Claude should activate.	3 / 3
Trigger Term Quality	Covers a strong set of natural terms a user would say — 'PHPCS', 'code style', 'coding standard', 'cs:fix', 'cs:check', 'PHP formatting', and 'CI PHPCS check has failed' — including common variations.	3 / 3
Distinctiveness Conflict Risk	It occupies a clear PHP/PHPCS-specific niche with distinct triggers, making it unlikely to fire for the wrong non-PHP skill.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: figlabhq/agent-skills
Commit: abac51b

Reviewed: 12 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.