← all publishers

lethilu4796

@lethilu4796 source repo

Report this profile Claim this profile

• 17 skills
• 0 followers
• 6 hours ago last updated

1. ▌
   Review · lethilu4796

   Run a comprehensive multi-perspective code review on recent changes. Also triggers on 'is this secure?', 'security review', 'check for vulnerabilities', 'could this be exploited?' for security-focused review.
   0
   installs
2. ▌
   Status · lethilu4796

   Show project status dashboard across registered repositories
   0
   installs
3. ▌
   DB Check · lethilu4796

   Validate database schema integrity and check for common issues
   0
   installs
4. ▌
   Changelog · lethilu4796

   Generate a changelog from git history since a tag, date, or commit
   0
   installs
5. ▌
   E2e Check · lethilu4796

   Run E2E tests or interactive browser verification. Triggers on: 'run e2e', 'e2e test', 'browser test', 'check in browser', 'verify UI', 'interactive test'.
   0
   installs
6. ▌
   Save Diary · lethilu4796

   MUST use when user says 'save diary', 'write diary', 'diary entry', 'update diary', or 'document session'. Also auto-trigger at the end of any significant session (feature shipped, major bug fixed, architecture decision, new project started).
   0
   installs
7. ▌
   Tech Radar · lethilu4796

   MUST use when user asks 'what's new?', 'any updates?', 'latest versions?', 'breaking changes?', 'should we upgrade?', 'what changed in X?', or when starting a new project to check if dependencies are current. Also trigger proactively at the start of major upgrade sessions.
   0
   installs
8. ▌
   Test Check · lethilu4796

   MUST use after implementing new features or bug fixes, when user asks 'run the tests', 'are tests passing?', 'test this', or before any deployment step. Also trigger when tests were previously failing and fixes were applied.
   0
   installs
9. ▌
   Review Diff · lethilu4796

   Scan git diffs for project-specific anti-patterns. Triggers on: 'scan diff', 'check diff', 'anti-pattern check', 'pattern scan', 'review changes'.
   0
   installs
10. ▌
    Session End · lethilu4796

    MUST use when user says 'bye', 'goodbye', 'good night', 'gnight', 'done for today', 'that's all', 'that's it', 'see you', 'see ya', 'let's stop', 'stopping here', 'wrapping up', 'signing off', 'closing down', 'done', 'finished for now', 'talk later', 'cya'. The user does NOT use slash commands — detect these natural session-ending phrases and run the full wrap-up automatically.
    0
    installs
11. ▌
    Sprint Plan · lethilu4796

    MUST use when user describes a multi-step feature to build, says 'let's build', 'new project', 'let's implement', or when a task clearly requires more than 3 steps and no plan exists yet. Do NOT trigger for simple additions like adding a comment, renaming a variable, or single-file changes.
    0
    installs
12. ▌
    Deploy Check · lethilu4796 bundle

    MUST use before any git push to main/master/production, or when user mentions 'deploy', 'going live', 'push to prod', 'ready to ship', 'merge to main', 'release'. Also trigger before any npm publish for CLI tools. Also triggers on: 'audit', 'check vulnerabilities', 'are our deps safe?', 'npm audit', 'yarn audit'.
    0
    installs
13. ▌
    Init Project · lethilu4796

    Init Project
    0
    installs
14. ▌
    Load Session · lethilu4796

    Restore session context at the start of every new conversation. Auto-triggers on session start, or when user says 'continue', 'what were we doing', 'where did we leave off'.
    0
    installs
15. ▌
    Save Session · lethilu4796

    MUST use when user says 'save', 'save session', or explicitly wants to preserve session state. {USER_NAME} does NOT use slash commands — also trigger proactively when significant work has been completed and session context should be persisted. For session endings (bye/done/goodbye), use the session-end skill instead which combines save-session + save-diary.
    0
    installs
16. ▌
    Register Project · lethilu4796

    Register an existing project in AI MemoryCore. Use when starting work on a new repo or when a project needs its own context file. Triggers on: 'register project', 'add project to memory', 'track this project', 'create project file'.
    0
    installs
17. ▌
    Elicit Requirements · lethilu4796

    Structured pre-feature requirements gathering. Run before writing any new feature or API endpoint to clarify scope, acceptance criteria, and technical constraints.
    0
    installs