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.
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines its purpose, provides comprehensive trigger terms covering tool names, commands, and natural language variations, and explicitly states when to activate. The description is specific to PHP code style tooling and would be easily distinguishable from other skills in a large skill library.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Fix PHP coding style issues using PHPCS and PHPCBF' - names the exact tools and the specific task being performed. | 3 / 3 |
Completeness | Clearly answers both what ('Fix PHP coding style issues using PHPCS and PHPCBF') and when ('Use this skill whenever...') with explicit trigger conditions including user mentions, file modifications, and CI failures. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'PHPCS', 'code style', 'coding standard', 'cs:fix', 'cs:check', 'PHP formatting', 'fix/check PHP code style', 'CI PHPCS check'. Includes both tool names and common user phrases. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with PHP-specific tools (PHPCS, PHPCBF), specific commands (cs:fix, cs:check), and clear niche around PHP code style. Unlikely to conflict with general code formatting or other language linters. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that efficiently communicates project-specific PHPCS configuration and workflow. It provides concrete, executable guidance with clear sequencing and validation steps. The content respects Claude's intelligence by focusing only on project-specific details (thresholds, sniff names, conventions) rather than explaining PHPCS basics.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only project-specific information Claude wouldn't know (custom thresholds, specific sniff names, project conventions). No unnecessary explanation of what PHPCS is or how PHP works. | 3 / 3 |
Actionability | Provides exact commands (`composer cs:fix`, `composer cs:check`), specific code examples with proper syntax, concrete thresholds (complexity 7/10), and copy-paste ready ignore directives and type hint examples. | 3 / 3 |
Workflow Clarity | Clear 4-step sequence with explicit validation checkpoint (step 4: re-run to confirm). Includes feedback loop instruction ('If new issues appear, fix those too'). The workflow handles the iterative fix-check cycle well. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections (Commands, Workflow, Common Issues, Scoping, CI). Content is appropriately sized for a single file (~80 lines). No need for external references given the scope, and sections are logically ordered from basic to advanced. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- figlabhq/agent-skills
- Commit
32c20f1
- Reviewed
Table of Contents
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.