li3p
14 verified skills
changelog
Generate human-readable changelog entries from git history and diffs. Use when preparing release notes, summarizing commits since a tag, or translating implementation commits into user-facing changes.
testing
debt-scan
Scan a repository for technical debt and prioritize remediation. Use when assessing project health, planning cleanup work, or turning code smells into actionable tickets.
development
dissect
Perform a deep structural review of a file, module, or directory. Use when the user asks for a focused code review of reliability, edge cases, error handling, dependencies, concurrency, or maintainability.
development
env-check
Validate a project's local development environment. Use when onboarding to a repo, returning after a break, or diagnosing missing runtimes, dependencies, env vars, services, migrations, or hooks.
development
explain-func
Add why-focused documentation to complex functions or code blocks. Use when the user asks to document dense logic, explain invariants, or add comments that help maintainers understand design intent.
development
migrate-draft
Draft a reversible database migration that follows existing project conventions. Use when adding, changing, renaming, indexing, or removing database schema elements.
data-ai
orient
Rebuild working context for the current repository. Use after clearing context, opening an old branch, resuming work, or when the user asks what state the repo is in.
development
refactor-safe
Refactor internal implementation without changing public API or behavior. Use when improving structure, readability, duplication, or complexity while preserving exported signatures, return shapes, errors, and tests.
development
ship
Validate a branch and draft a pull request description from real commits and diffs. Use when preparing a PR, checking branch readiness, or writing reviewer-facing release context.
testing
testmatch
Generate tests that match an existing project's testing style. Use when adding coverage for a target file, function, bug fix, or edge case while preserving local conventions.
testing
preflight
Scan staged changes before commit for debug artifacts, secrets, skipped tests, generated files, and obvious code smells. Use when preparing a commit or checking whether staged changes are clean.
development
notion-publish
Publish a local Markdown file to a Notion page using marknotion. Use when the user wants to push README, docs, changelogs, or any Markdown content to Notion, either updating an existing page or creating a new one under a parent page.
documentation
notion-search
Search Notion for pages or databases by query using marknotion. Use when the user references a Notion page by name rather than URL, when locating a page to publish to or pull from, or when discovering what trackers and docs exist in the connected workspace.
documentation
notion-pull
Export a Notion page to local Markdown using marknotion. Use when the user wants to pull a spec, design doc, meeting notes, or any Notion page into the repository as a Markdown file, or wants to read Notion content as context for a task.
documentation