// Use "component: Brief summary" format for the commit title. Use when this capability is needed.
[HINT] Download the complete skill directory including SKILL.md and all related files
| name | commit |
| description | Use "component: Brief summary" format for the commit title. Use when this capability is needed. |
Use "component: Brief summary" format for the commit title.
Examples:
Provide a brief prose summary of the purpose of the changes made. Use backticks for code elements (function names, variables, file paths, etc.).
Ensure the maximum line length never exceeds 72 characters.
When referencing external GitHub PRs or issues, use proper GitHub interlinking format: "owner/repo#123"
If you wrote code yourself, include a "Written by Claude" footer at the end of the commit message. No emoji.
However, when simply asked to write a commit message (without having written the code), there's no need to add that footer.
search: Cancel pending requests when UI components close
Add `SearchManager.cancelPendingRequests()` to allow components to
cancel their queued search requests when being destroyed. Apply this
to both `SemanticNoteFinder` and `RelatedNotesView` to prevent
unnecessary embedding requests after modals/views are closed.
Also extract `COMPONENT_ID` constants for consistent component
identification.
See the "Git operations" section in CLAUDE.md.
Converted and distributed by TomeVault — claim your Tome and manage your conversions.