quality-check
Use when the user finishes a code change and wants format / lint / type-check / tests run together, or asks "is this clean?" / "any issues?". On-demand replacement for prior chained quality gates.
What this skill does
# On-demand quality check
Prior plugins ran format + lint + type-check on every Write/Edit via PostToolUse hooks, adding ~3.5min latency per edit. SiftCoder replaces that with this on-demand skill.
## Default sequence
Detect tooling from the project root, then run in parallel:
1. **Format check** — `prettier --check`, `dotnet format --verify-no-changes`, `gofmt -l`, `cargo fmt --check`, `apex-format` (sf-cli) — pick what exists.
2. **Lint** — `eslint`, `tsc --noEmit` (for TS), `pylint`/`ruff`, `golangci-lint`, `cargo clippy`, `pmd` (Apex) — pick what exists.
3. **Type-check** — `tsc --noEmit`, `mypy`, `pyright`, `cargo check` — pick what exists.
4. **Tests** — only if the user said "test" or "run tests". Otherwise skip; tests can be slow.
## Pattern
Use the `Bash` tool with multiple parallel calls in one message. Report a compact summary:
```
✓ format no diffs
✗ lint 3 errors in src/foo.ts:14, src/bar.ts:7, src/bar.ts:22
✓ types ok
- tests skipped (use /siftcoder:quality --tests)
```
If there are failures, **fix them** unless the user said report-only.
## Salesforce projects
For sfdx projects, the canonical chain is:
```bash
sf project deploy validate --source-dir force-app
sf code analyzer run -t force-app
npx prettier --check 'force-app/**/*.{cls,trigger,xml}'
```
Use `sfdx scanner:run` for legacy orgs; `sf code-analyzer run` for v2.
## When to skip
- User is mid-thought, hasn't asked for it.
- Change is a comment or doc-only edit.
- Pre-commit hook will run it anyway.
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.