phpstan-fixer
Fix PHPStan static analysis errors by adding type annotations and PHPDocs. Use when encountering PHPStan errors, type mismatches, missing type hints, or static analysis failures. Never ignores errors without user approval.
What this skill does
# PHPStan Error Fixer
Fix PHPStan static analysis errors through proper type annotations, PHPDocs, and
code improvements. This skill teaches agents how to resolve errors without
suppressing them, respecting the project's configured strictness level.
## Core Principles
1. **Never suppress errors as first resort** — Fix the root cause with proper
types and annotations
2. **Respect user configuration** — Never modify `phpstan.neon` settings
(level, paths, parameters)
3. **No silent ignoring** — Never add `ignoreErrors` to config without explicit
user approval
4. **Context-aware fixes** — Understand the project type (Laravel, Symfony,
vanilla PHP) before proposing solutions
5. **Ask before ignoring** — If a legitimate ignore is needed, explain why and
get user approval first
6. **Don't fix third-party code** — Never modify files in `vendor/`. Use stub
files instead to override wrong types
## Workflow
### Step 1: Understand the Project Context
Before fixing errors, identify the project type:
```bash
# Check for Laravel
grep laravel/framework composer.json
# Check for Symfony
grep symfony/symfony composer.json
# Check for PHPStan extensions
grep phpstan composer.json
# Read PHPStan config
cat phpstan.neon
# Check project guidelines
cat AGENTS.md
```
**Key information to extract:**
- PHPStan level (0-10, or max)
- Installed PHPStan extensions (larastan, phpstan-strict-rules, etc.)
- Framework-specific helpers (Laravel IDE Helper, Symfony plugin)
- Project-specific type conventions
### Step 2: Analyze the Error
PHPStan errors have this structure:
```text
------ ----------------------------------------------
Line /path/to/File.php
------ ----------------------------------------------
42 Parameter $user of method foo() has invalid
type App\User.
💡 Identifier: parameter.type
------ ----------------------------------------------
```
**Extract:**
1. **Error identifier** (e.g., `parameter.type`, `missingType.return`)
2. **Error location** (file, line number)
3. **Context** (what's the code trying to do?)
### Step 3: Apply the Right Fix
Use the error identifier to determine the fix strategy:
### Step 4: Verify the Fix
After applying fixes, run PHPStan again to confirm:
```bash
vendor/bin/phpstan analyse
```
**Important:**
- If new errors appear, the fix may have been incorrect. Re-analyze the error and try a different approach.
- If the same error persists, the fix wasn't applied correctly. Double-check the code.
- If errors are resolved, mark the fix as successful and move to the next error.
---
## Common Error Fixes
### Type-Related Errors
#### `missingType.parameter` — Missing parameter type
**Error:**
```text
Parameter $name has no type specified.
```
**Fix — Add native type:**
```php
// Before
function greet($name) {
return "Hello, $name";
}
// After
function greet(string $name): string {
return "Hello, $name";
}
```
**Fix — Use PHPDoc for complex types:**
```php
// Before
function processUsers($users) { ... }
// After
/**
* @param array<int, User> $users
*/
function processUsers(array $users): void { ... }
```
---
#### `missingType.return` — Missing return type
**Error:**
```text
Method foo() has no return type specified.
```
**Fix — Add native return type:**
```php
// Before
public function getUser() {
return $this->user;
}
// After
public function getUser(): User {
return $this->user;
}
```
**Fix — Use PHPDoc for union/intersection types:**
```php
// Before
public function findUser($id) { ... }
// After
/**
* @return User|null
*/
public function findUser(int $id): ?User { ... }
```
---
#### `argument.type` — Wrong argument type
**Error:**
```text
Parameter #1 $id of method find() expects int, string given.
```
**Fix — Cast the argument:**
```php
// Before
$user = $repository->find($request->input('id'));
// After
$user = $repository->find((int) $request->input('id'));
```
**Fix — Narrow the type earlier:**
```php
// Better approach
$id = $request->integer('id'); // Laravel helper
$user = $repository->find($id);
```
---
#### `return.type` — Wrong return type
**Error:**
```text
Method foo() should return User but returns User|null.
```
**Fix — Adjust return type:**
```php
// Before
public function getUser(): User {
return $this->user ?? null;
}
// After
public function getUser(): ?User {
return $this->user ?? null;
}
```
**Fix — Ensure non-null with assertion:**
```php
public function getUser(): User {
assert($this->user !== null);
return $this->user;
}
```
---
### Property Errors
#### `property.notFound` — Undefined property access
**Error:**
```text
Access to an undefined property User::$name.
```
**Fix — Add property declaration:**
```php
class User {
private string $name;
public function __construct(string $name) {
$this->name = $name;
}
}
```
**Fix — Document magic property:**
```php
/**
* @property string $name
*/
class User {
public function __get($key) { ... }
}
```
**Fix (Laravel) — Use IDE Helper:**
```bash
# Generate PHPDocs for Eloquent models
php artisan ide-helper:models
```
---
#### `property.onlyWritten` — Property written but never read
**Error:**
```text
Property User::$name is never read, only written.
```
**Fix — Remove unused property or add getter:**
```php
// If truly unused, remove it
// If needed, add usage:
public function getName(): string {
return $this->name;
}
```
---
### Method Errors
#### `method.notFound` — Undefined method call
**Error:**
```text
Call to an undefined method App\User::getFullName().
```
**Fix — Add method:**
```php
class User {
public function getFullName(): string {
return $this->first_name . ' ' . $this->last_name;
}
}
```
**Fix — Document magic method:**
```php
/**
* @method string getFullName()
*/
class User {
public function __call($method, $args) { ... }
}
```
**Fix (Laravel) — Add to `@mixin` for query builders:**
```php
/**
* @mixin \Illuminate\Database\Eloquent\Builder
*/
class User extends Model { ... }
```
---
### Array/Offset Errors
#### `offsetAccess.notFound` — Undefined array offset
**Error:**
```text
Offset 'email' does not exist on array.
```
**Fix — Use array shape PHPDoc:**
```php
/**
* @param array{email: string, name: string} $data
*/
function createUser(array $data): void {
echo $data['email']; // PHPStan knows this exists
}
```
**Fix — Add existence check:**
```php
if (isset($data['email'])) {
echo $data['email'];
}
```
**Fix — Use null coalescing:**
```php
$email = $data['email'] ?? '[email protected]';
```
---
### Generics Errors
#### `missingType.generics` — Missing generic type
**Error:**
```text
Class Collection has @template T but does not specify it.
```
**Fix — Specify generic type in PHPDoc:**
```php
// Before
/** @var Collection $users */
$users = User::all();
// After
/** @var Collection<int, User> $users */
$users = User::all();
```
**Fix (Laravel) — Use IDE Helper stubs for collections.**
---
### Dead Code Errors
#### `deadCode.unreachable` — Unreachable code
**Error:**
```text
Unreachable statement - code above always terminates.
```
**Fix — Remove dead code:**
```php
// Before
function foo() {
return true;
echo "This never runs"; // Error
}
// After
function foo() {
return true;
}
```
---
#### `identical.alwaysTrue` / `identical.alwaysFalse` — Condition is always true/false
**Error:**
```text
Strict comparison using === between int and string will always evaluate to false.
```
**Fix — Remove useless condition or fix type:**
```php
// Before
if ($id === '123') { ... } // $id is int
// After
if ($id === 123) { ... }
```
---
## Framework-Specific Fixes
### Laravel
**Install Larastan for Laravel-aware analysis:**
```bash
composer require --dev larastan/larastan
```
**Check `phpstan.neon` includes Larastan** (ask user to add if missing):
```yaml
includes:
- vendor/larastan/larastan/extension.neon
```
**Common Laravel Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.