Review OnPush components with host bindings after Angular 18 when host-bound state or external callbacks may not refresh as expected. Use when a bounded slice relies on ChangeDetectionStrategy.OnPush, host bindings, markForCheck, detectChanges, or manual refresh logic.
Scanned 10/2/2026
npx -y skills add janpereira-dev/ngAutoPilot --skill angular--upgrade--change-detection--angular-onpush-host-bindings-v18 --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Angular Upgrade Change Detection Angular Onpush Host Bindings V18?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/janpereira-dev-angular-upgrade-change-detection-angular-onpush-ho)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
id: angular.upgrade.change-detection.angular-onpush-host-bindings-v18
name: Angular OnPush Host Bindings v18
description: >
Review OnPush components with host bindings after Angular 18 when host-bound state or external callbacks may not refresh as expected. Use when a bounded slice relies on ChangeDetectionStrategy.OnPush, host bindings, markForCheck, detectChanges, or manual refresh logic.
stack:
- Angular
- TypeScript
category: change-detection
status: stable
version: 0.10.0
owner: NgAutoPilot
triggers:
- OnPush
- host bindings
- markForCheck
- detectChanges
compatibility:
angular:
min: "18"
---
# Angular OnPush Host Bindings v18 Migration
## Purpose
Review OnPush components with host bindings after Angular 18.
## When to Use
- Components use `ChangeDetectionStrategy.OnPush`.
- Components rely on `@HostBinding`.
- Manual refresh logic exists.
## When Not to Use
- The app does not use OnPush or host bindings.
- The app is still in a version upgrade.
## Required Inputs
- OnPush components
- host bindings
- manual refresh logic
- tests for the target slice
## Procedure
1. Identify OnPush components with host-bound state.
2. Review external callback and refresh behavior.
3. Add explicit dirty-marking where needed.
4. Validate tests and UI state.
## Do
- Keep refresh triggers intentional.
- Validate third-party callback paths.
- Review visual state updates.
## Do Not
- Do not rely on implicit refresh behavior.
- Do not mix this with the version upgrade.
## Review Checklist
- [ ] Host-bound state updates correctly.
- [ ] Refresh logic is explicit.
- [ ] Tests pass.
## Expected Output
1. OnPush host binding summary.
2. Refresh logic updates.
3. Test result.
## Exit Criteria
- OnPush host binding risk is explicit.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!