aimate

Plugin aimate from marketplace aicelerate in Dawn-Technology/aicelerate. Commands read from the repo's manifest — yesterday.

Skills (22)

• asvs-audit

  Static OWASP ASVS 5.0 Level 1 security audit of a codebase. Checks all 70 Level 1 requirements plus other security issues found on the way, verifies every finding against the code to remove false positives, runs the package manager's dependency audit, and writes a report to docs/. Use this when aske

• code-review

  Reusable review core for structured findings on supplied code or diffs. Invoked by review-pr, review-local, and the pre-push self-review in resolve-pr-feedback; not for reviewing a PR/MR or local working tree directly, use those skills instead.

• configure-mcp

  Validate and configure project- or client-specific GitHub, GitLab, Jira/Confluence, Figma, Sentry, and Playwright tooling through a short interactive wizard, choosing CLI or MCP where both support the capability. Use when a user asks to install, set up, configure, repair, change, or onboard Aimate i

• estimate-size

  Estimate software tickets and work items with a configurable relative-sizing workflow. Respect dedicated estimators and local project rules, and use the built-in defaults when no local rules are provided.

• estimate-time

  Add a time estimate in hours to an existing implementation plan. Use when the user asks to estimate a plan or task list, or asks how long the work will take.

• fetch-ticket

  Reusable ticket reader that resolves a Jira work item, GitHub Issue, or GitLab Issue through the project's saved route and returns it as one provider-neutral ticket with every comment verbatim. Invoked by prepare-ticket and implement-ticket; not for validating or implementing a ticket directly, use

• fix-ci

  Use when asked to fix, unblock, or babysit failing CI on a PR or MR — "fix the CI on this PR", "the pipeline is red on MR 42", "lint and type checks are failing", "make the checks pass", "keep this PR green" — or to update it from main and resolve merge conflicts. Takes a PR/MR number or URL. First

• implement-ticket

  Use when asked to implement, build, or pick up a ticket end to end — a Jira work item, GitHub Issue, or GitLab Issue — including "implement ABC-123", "implement gh issue #137", "work on issue 137", or "pick up this ticket". Critiques the request against the code, builds it in a throwaway git worktre

• prepare-ticket

  Use when asked whether a ticket or issue is ready for development or to be picked up, or to prepare, validate, refine, challenge, or sanity-check a Jira work item, GitHub Issue, or GitLab Issue before building it — "is this ticket ready?", "can a developer pick this up?", "check this ticket before w

• resolve-pr-feedback

  Use when asked to resolve, address, fix, or reply to review feedback on a GitHub Pull Request or GitLab Merge Request, including review comments, unresolved threads, requested changes, or "apply the review comments" requests.

• review-and-resolve-pr

  Use when asked to review a GitHub Pull Request or GitLab Merge Request and act on the result in one autonomous pass, including "review and fix this PR", "review this MR and resolve the feedback", "close the review loop on this PR", or any request that pairs reviewing a PR/MR with applying the findin

• review-architecture

  Read-only architecture and design-quality review of an existing codebase. Finds hot spots from git churn, file growth, complexity and files that change together, then checks them against layering, dependency direction, cohesion, SOLID, simplicity, test safety and platform-support rules (runtime and

• review-local

  Use when reviewing local code before committing and the user wants findings for a file, folder, uncommitted changes, staged changes, commits, patches, or snippets without involving a pull request or merge request.

• review-pr

  Use when asked to review a GitHub Pull Request or GitLab Merge Request, including PR/MR URLs, identifiers, discussions, findings, inline comments, approvals, or request-changes actions.

• split-spec

  Use when asked to break down, split, cut or carve a spec, feature, epic or any larger piece of work into tickets — including "break this work down into tickets", "split this spec", "turn this into tickets", "maak hier tickets van" or "knip deze spec op" — and the input is bigger than one ticket. Pro

• test-pr-e2e

  Test a PR or MR like a human QA engineer using Playwright MCP. Analyzes the diff (or diffs, for a multi-service/microservice feature spanning several PRs) to generate a scenario list (Phase 1), then executes each scenario live in a browser with inline logging and screenshots (Phase 2). Use when aske

• test-pr-guide

  Use when the user wants to know how to manually test code changes on a branch or PR - analyzes the diff, identifies what changed, and produces a step-by-step guide a real person can follow to verify the feature or fix works, including any required setup like fixtures, mock SPs, or config. Also use w

• validate-ticket

  [DEPRECATED] Renamed to prepare-ticket. Use only when validate-ticket is named explicitly; otherwise use prepare-ticket.

• write-commit-message

  Writes high-quality git commit messages following the seven rules of great commit messages (Chris Beams) and a fixed subject+body template. Auto-triggers whenever a commit is being authored or suggested — e.g. the user asks to "commit", "commit this", "git commit", or the agent itself is about to ru

• write-plan

  Turn a prepared ticket into a task breakdown with sizes: something to discuss the approach with, take into refinement, or estimate from. Use when the user asks for an implementation plan, to break a ticket down into an implementation plan or into tasks, or to size the work. Input is the brief that p

• write-prd

  Create a PRD and user stories through user interview, codebase exploration, and component design. Use when user wants to write a PRD, create a product requirements document, user stories or plan a new feature.

• write-readme

  Use this skill whenever the user asks to create, write, generate, improve, or standardize a README for a codebase or repository, or mentions that a project is missing documentation. Applies to any language or stack (dotnet, Node, Python, etc). Always use this skill instead of freestyling a README st

Similar plugins