Turns a PRD, feature brief, or existing requirements into a complete Technical Requirements/Design Document (TRD) and saves it under docs/TRDs/ -- never implements the request, only documents the technical solution. Use when the user asks to write/draft a TRD, design the technical solution for a feature, or turn a PRD…
Returns a reference snapshot of a Jira project: its issue types, workflow statuses, components, priorities, assignable users, and labels in use. Use for "what statuses does this project use", "who's on this project", "what labels exist" -- or before filtering JQL on a status/label/assignee you're not sure is real, to…
Writes or updates an AGENTS.md file for a target project (or, for a monorepo, a root AGENTS.md plus nested per-subproject AGENTS.md files) -- the open, tool-agnostic convention (agents.md) that gives a coding agent the build/test/architecture/style context a README doesn't. Infers the project's real structure from…
Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction. Use when a session is approaching a context limit and a task phase is a natural place to compact.
Adds a comment to a Confluence page. Use for "leave a comment on page X saying Y" or "comment on this page". This is a write operation gated behind explicit user confirmation.
Creates a new Confluence page in a space, optionally as a child of an existing page. Use for "create a page in X called Y" or "add a new page under Z". This is a write operation gated behind explicit user confirmation.
Permanently deletes a Confluence page. Use for "delete page X" or "remove the old draft page". This is a destructive write operation gated behind explicit user confirmation.
Fetches a single Confluence page's content and metadata by its content id. Use for "what does page X say", "show me page 12345678", or as the first step in summarizing/editing a page once you know its id. This is a read-only operation.
Enumerates every Confluence space visible to the authenticated user. Use for "what spaces are there", "what's the key for the engineering space", or before creating a page when the destination space key isn't already known. This is a read-only operation.
Runs an arbitrary CQL query against Confluence and returns structured page results. Use for "find pages about X", "search Confluence for Y", or any lookup not covered by a more specific Confluence skill. This is a read-only operation.
Updates an existing Confluence page's title and/or content. Use for "update page X to say Y", "add a section about Z to the runbook", or "rename this page". This is a write operation gated behind explicit user confirmation.
High-level Confluence assistant. Answers questions like "what does the onboarding page say", "find the runbook for X", "summarize this page", and creates/updates pages, comments, and labels -- by calling structured Confluence tools and reasoning over their JSON output, never by guessing or inventing page content. Use…
Turns a Jira ticket into a reviewed pull request: reads the project's own AGENTS.md and existing git history for its conventions, fetches the ticket, plans the change, scaffolds and implements it, writes tests, runs the project's local quality gate, then commits and opens a PR -- pausing for explicit user confirmation…
Sanitizes a repository's code comments and implementation documentation so they describe the current software, not the conversation, meeting, or decision process that produced it. Scans structure lightly, asks the user which scope to inspect, classifies each comment/doc item as KEEP, REWRITE, REMOVE, or REVIEW, and…
Explains a topic as a compressed mental model rather than an information dump. Selects the highest-leverage concepts, makes mechanisms and causal structure explicit, anchors new ideas to what the user already knows, uses prediction and retrieval when they add learning value, corrects the most consequential…
Reverse-engineers an existing, under-documented codebase into a GitHub Spec Kit baseline -- constitution, per-capability specs, plans, data models, and contracts, with known defects and gaps beside each spec -- precise enough to reimplement it with identical behavior, so the specs become the source of truth. Analyzes…
Verifies that a project's specifications (GitHub Spec Kit layout: constitution, spec.md, plan.md, data-model.md, contracts/) accurately describe the code, without anyone reading every document. Runs checks in order of cost -- static checks and existing tests automatically, then asks before running the system, an…
Reviews a git diff (working-tree changes, a commit range, or an explicitly named PR/branch/file) for correctness bugs and code-quality issues -- wrong conditions, removed invariants, broken call sites, duplicated logic, unnecessary complexity, wasted work, fixes at the wrong depth, and convention violations -- using…
Reads a file, or lists a directory, from a GitLab project's repository at a branch/tag/commit. Use for "show me src/app.py on main", "what's in the docs folder of group/repo". Read-only.
Posts, edits, or deletes a comment on a GitLab merge request -- a general note or an inline comment on a specific diff line (new comments optionally as an unpublished draft). Routes to addmrnote, addmrdiscussion, editmrnote, or deletemrnote from what's being asked. Use for "comment on MR 42", "leave this note on line…
Returns the per-file unified diffs of a GitLab merge request, optionally for one file. Use for "show me the changes in MR 42" or as the input to a code review of a remote MR. Read-only.
Fetches one GitLab merge request's details (branches, state, reviewers, diffrefs) and every discussion thread on it. Use for "what's MR 42 about", "what has been said on this MR", or before reviewing/commenting on one. Read-only.
Lists GitLab merge requests -- in one project or instance-wide -- by state, scope, reviewer, or search text. Use for "my open MRs", "MRs waiting on my review", "find the MR about X". Read-only.
GitLab (self-hosted or gitlab.com) assistant. Answers questions like "what's in MR 42", "show me src/app.py on main", "what MRs are waiting on my review", and posts, edits, or deletes general or inline comments on merge requests -- by calling structured GitLab tools and reasoning over their JSON output, never by…
★not rated 13
changed 15d agoA105 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: