knowledgine

Create Conventional Commits with type prefix, breaking change detection, dry-run preview, and strict rules against ticket IDs in messages. **AUTOMATICALLY USE** when: (1) Creating git commits ("commit", "git commit") (2) Suggesting commit messages ("commit message") (3) Splitting commits ("split commits") (4) Fixing commit messages ("fix commit") (5) Any git commit related request

Orchestrate the full release process: push to develop, generate release summary, propose version bump, update package.json files, generate CHANGELOG, create release PR, and monitor CI. Supports dry-run preview mode. **AUTOMATICALLY USE** when: (1) Releasing a new version ("release", "cut a release", "prepare release") (2) Bumping version ("version bump", "bump version") (3) Creating release PRs ("release PR") (4) Generating changelogs ("changelog", "release notes") (5) Any release-related request

Record knowledge to the local knowledge base after solving problems, making design decisions, or discovering reusable patterns. Invoke whenever you have just fixed a bug, made an architectural choice, found a reusable pattern, learned something from external sources, or completed a refactoring. Capturing while context is fresh prevents knowledge loss across sessions.

Search the local knowledge base for past solutions, design decisions, and patterns before starting work. Invoke when facing an error or exception, when approaching an unfamiliar area of the codebase, or when considering implementation approaches. Prevents re-solving already-solved problems and surfaces relevant context proactively.

Get contextual knowledge suggestions based on the current work context — the file being edited, the task being performed, or the error being investigated. Invoke at the start of a work session, when opening a new file, or when beginning a feature. Surfaces relevant past knowledge proactively without requiring a specific query.

Analyze existing codebase to inform spec design. Scans specified packages or directories to extract architecture patterns, public APIs, dependency relationships, and test coverage. Output feeds directly into design.md.

Close out a completed spec. Verifies all acceptance criteria are met, updates spec status to completed, captures knowledge learned during implementation, and updates the spec index.

Generate a handoff report for transitioning work between tools (Claude Code to Cursor, or vice versa). Summarizes spec status, progress, decisions made, and how to continue.

Implement features by working through tasks.md step by step with TDD. Reads the full spec (requirements.md, design.md, tasks.md), implements each task in order, and updates progress. Works in both Claude Code and Cursor.

Initialize a new SDD spec directory with templates. Creates specs/KNOW-{NNN}-{description}/ with requirements.md, design.md, and tasks.md populated from templates. Auto-assigns the next available ticket number.

Perform a comprehensive spec compliance review. Combines AGENTS.md review checklist with spec-specific checks against requirements.md, design.md, and tasks.md. Produces a structured review report with pass/fail/warn per item.

Generate or refine the three SDD spec files (requirements.md, design.md, tasks.md) for an existing spec directory. Analyzes the codebase, conducts user dialogue for requirements, and produces implementation-ready specifications.

Display a dashboard of all specs and their progress. Shows status, completion percentage, and last update for each spec in specs/. Quick overview of the SDD pipeline.

Synchronize specs/tasks.md with Plans.md. Expands spec tasks into Plans.md format with spec reference links, and reflects Plans.md completions back to tasks.md. Bridges SDD and Harness workflows.

Validate that implementation satisfies spec acceptance criteria. Maps each criterion in requirements.md to corresponding tests, runs them, and reports pass/fail per criterion. Use after implementation, before PR creation.