personal-projects/leo-claude-mktplace
Template
0
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[Sprint 3] feat: Implement SessionStart auto-validate hook for contract-validator #229

New Issue
Closed
opened 2026-01-27 21:51:35 +00:00 by lmiranda · 0 comments
lmiranda commented 2026-01-27 21:51:35 +00:00
Owner
Copy Link

Description

Implement smart mode SessionStart hook that validates plugin compatibility only when files changed since last check.

Implementation

Wiki: Sprint 3: Hooks Implementation

Plugin: plugins/contract-validator/

Technical Details

Hook Configuration

  • Event: SessionStart
  • Behavior: Conditional validation

Smart Mode Logic

  1. Check .contract-validator-lastcheck file
  2. Compare timestamps with git changes
  3. Skip if no changes, validate if changes found

Files to Monitor

  • plugins/**/plugin.json
  • plugins/**/hooks/hooks.json
  • plugins/**/commands/*.md
  • mcp-servers/**/

Files to Create/Modify

plugins/contract-validator/hooks/
  hooks.json         # SessionStart hook
  auto-validate.sh   # Smart validation script

Acceptance Criteria

  • Hook in hooks/hooks.json
  • Tracks last validation timestamp
  • Skips when no changes
  • Validates when changes detected
  • Clear output messages

Dependency

Provides foundation for Breaking Change Detection feature.

Technical Notes

CRITICAL: Hooks must be in hooks/hooks.json, NOT inline in plugin.json.

## Description Implement smart mode `SessionStart` hook that validates plugin compatibility only when files changed since last check. ## Implementation **Wiki:** [Sprint 3: Hooks Implementation](https://gitea.hotserv.cloud/personal-projects/leo-claude-mktplace/wiki/Change-V5.2.0%3A-Plugin-Enhancements-Proposal-%28Sprint-3-Hooks%29) **Plugin:** `plugins/contract-validator/` ## Technical Details ### Hook Configuration - **Event:** `SessionStart` - **Behavior:** Conditional validation ### Smart Mode Logic 1. Check `.contract-validator-lastcheck` file 2. Compare timestamps with git changes 3. Skip if no changes, validate if changes found ### Files to Monitor - `plugins/**/plugin.json` - `plugins/**/hooks/hooks.json` - `plugins/**/commands/*.md` - `mcp-servers/**/` ### Files to Create/Modify ``` plugins/contract-validator/hooks/ hooks.json # SessionStart hook auto-validate.sh # Smart validation script ``` ## Acceptance Criteria - [ ] Hook in `hooks/hooks.json` - [ ] Tracks last validation timestamp - [ ] Skips when no changes - [ ] Validates when changes detected - [ ] Clear output messages ## Dependency Provides foundation for Breaking Change Detection feature. ## Technical Notes **CRITICAL:** Hooks must be in `hooks/hooks.json`, NOT inline in plugin.json.
lmiranda added the Type/FeaturePriority/HighEffort/MComplexity/Medium labels 2026-01-27 21:51:35 +00:00
lmiranda added this to the Sprint 3 - Hooks milestone 2026-01-27 21:55:30 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Component/API
API endpoints, contracts, and integration
 Component/Auth
Authentication and authorization
 Component/Backend
Backend service code and business logic
 Component/Database
Database schemas, migrations, queries
 Component/Deploy
Deployment, infrastructure, DevOps
 Component/Docs
Documentation and guides
 Component/Frontend
User interface and client-side code
 Component/Infra
Infrastructure and system configuration
 Component/Testing
Test infrastructure and frameworks
 Tech/Docker
Docker containers and compose
 Tech/FastAPI
FastAPI backend framework
 Tech/JavaScript
JavaScript/Node.js code
 Tech/PostgreSQL
PostgreSQL database
 Tech/Python
Python language and libraries
 Tech/Redis
Redis cache and pub/sub
 Tech/Vue
Vue.js frontend framework
Complexity/Complex
High uncertainty or many dependencies
 Complexity/Medium
Some unknowns or dependencies
 Complexity/Simple
Straightforward, well-understood
 Effort/L
3-5 days
 Effort/M
1-2 days
 Effort/S
2-4 hours
 Effort/XL
> 1 week
 Effort/XS
< 2 hours
 Priority/Critical
Immediate attention required
 Priority/High
Important, needs attention soon
 Priority/Low
Nice to have, can wait
 Priority/Medium
Normal priority
 Type/Bug
Something isn't working
 Type/Chore
Maintenance tasks
 Type/Documentation
Documentation improvements
 Type/Feature
New feature or request
 Type/Refactor
Code refactoring without changing behavior
 Type/Test
Testing related
No Label Complexity/Medium Effort/M Priority/High Type/Feature
Milestone
No items
No Milestone Sprint 3 - Hooks
Projects
Clear projects
No project
Assignees
Clear assignees
lmiranda
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: personal-projects/leo-claude-mktplace#229
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?