imvanzen
11 verified skills
codebase-analysis
Analyse the codebase of the system. Look for dependencies. Understand how the business logic is implemented. Look for duplications.
development
maintenance
Resolves dependency audit (security) issues and updates outdated packages with prioritization by breaking-change risk and security/value. Prefer security fixes and non-breaking updates; defer or flag major upgrades. Use when the user asks to fix audit, update packages, resolve vulnerabilities, or run maintenance.
testing
create-pull-request
Creates GitHub pull requests with conventional titles, template-filled bodies, labels, and assignees using the GitHub MCP server. Use when the user asks to create a PR, open a PR, submit changes for review, or says their branch is ready for review.
tools
code-review
Perform code review. Quality analysis. Acceptance criteria verification. Best practices review.
development
e2e-testing
E2E testing patterns, verification procedures, and CI readiness checklists using Playwright. Use for writing, debugging, or reviewing end-to-end tests, fixing flaky tests, creating Page Objects, mocking external APIs.
development
technical-context-discovery
Discover and establish technical context before implementing any feature. Prioritize project instructions, existing codebase patterns, and external documentation in that order. Use for any task requiring understanding of project conventions, coding standards, architecture patterns, and established practices before writing code.
development
task-analysis
Analyse task description, performs gap analysis, expand the context for the task, analyse the current state of the system in the context of the task, helps build PRD, creates a context for the task, gathers information about the task from different sources.
development
implementation-gap-analysis
Implementation gap analysis. Verify what has to be implemented. Verify what was implemented. Compare plan to current state.
testing
create-branch
Creates a feature branch from repo default (main) using project branching convention. Derives branch name from PAIC ticket (via Jira MCP), from a short description, or from uncommitted changes. Use when the user wants to create a branch, start work on a ticket, or switch off main before committing.
tools
commit-series-on-branch
Creates a logical series of commits from current changes; never commits to main; ensures or uses a working/feature branch so changes stay isolated and reviewable via PR. Use when the user wants to split changes into multiple commits, "commit my work", "create commits from changes", or to prepare changes for PR on a branch.
data-ai
architecture-design
Design the architecture to solve a given task. Propose the solutions to be used to deliver the task following the best practices and standards.
content-media