What you can ask · Gunnie.ai docs

How asking works

You do not need to name a tool. Ask the way you would ask a colleague, and mention a ticket key, a pull request number or a product when you have one. Replace ABC-123, ABC-100 and #42 in the examples with your own.

If a question needs a tool your role does not have, or something outside what your organisation’s connections allow, Gunnie.ai refuses that call and your assistant tells you so. The refusal is in the call log with the rule that stopped it.

Reader

Looks up products and tickets and sees the story behind a ticket.

Can propose: Contact Gunnie.

Questions to try

“What can you do for me with Gunnie.ai, given my role?”
“Which tickets are assigned to me, and which of them should I pick up first?”
“Give me the full story behind ABC-123: what was decided, by whom, and what is still open.”
“How is the current sprint going: what is done, what is in progress and what is at risk?”
“Find products matching "wall plug 8 mm" and show their price and stock.”
“Find the Confluence page about our release process and summarise it in five points.”

Ticket creator

As reader, and creates tickets.

Can propose: Create ticket, Add comment, Contact Gunnie.

Questions to try

“What can you do for me with Gunnie.ai, given my role?”
“Which tickets are assigned to me, and which of them should I pick up first?”
“Give me the full story behind ABC-123: what was decided, by whom, and what is still open.”
“How is the current sprint going: what is done, what is in progress and what is at risk?”
“Find products matching "wall plug 8 mm" and show their price and stock.”
“Find the Confluence page about our release process and summarise it in five points.”

Designer

Works from designs and tickets, and comments on tickets.

Looks up: Who am I, What can I ask, Search products, Product in the PIM, Search issues, Ticket context, My issues, Sprint overview, Backlog, Epic overview, Dependencies, Search Confluence, Read Confluence page, Design from Figma, Action result.

Can propose: Create ticket, Add comment, Contact Gunnie.

Questions to try

“What can you do for me with Gunnie.ai, given my role?”
“Which tickets are assigned to me, and which of them should I pick up first?”
“Give me the full story behind ABC-123: what was decided, by whom, and what is still open.”
“How is the current sprint going: what is done, what is in progress and what is at risk?”
“Find products matching "wall plug 8 mm" and show their price and stock.”
“Find the Confluence page about our release process and summarise it in five points.”

Business analyst

Reads and refines tickets and documentation, and proposes comments and field changes.

Can propose: Create ticket, Add comment, Update ticket fields, Create sub-task, Link tickets, Contact Gunnie.

Questions to try

“What can you do for me with Gunnie.ai, given my role?”
“Which tickets are assigned to me, and which of them should I pick up first?”
“Give me the full story behind ABC-123: what was decided, by whom, and what is still open.”
“How is the current sprint going: what is done, what is in progress and what is at risk?”
“Is there a branch or pull request for ABC-123 yet, and what state is it in?”
“Find products matching "wall plug 8 mm" and show their price and stock.”

Product owner

Works the backlog: sprints, epics, releases and ticket history, and proposes changes to tickets.

Looks up: Who am I, What can I ask, Search products, Product in the PIM, Search issues, Ticket context, My issues, Sprint overview, Backlog, Epic overview, Ticket history, Release overview, Recently finished, Dependencies, Search Confluence, Read Confluence page, Pull requests, Ticket code status, Pull request details, Pipeline status, Compare branches, Design from Figma, Action result.

Can propose: Create ticket, Add comment, Move ticket, Update ticket fields, Create sub-task, Link tickets, Contact Gunnie.

Questions to try

“What can you do for me with Gunnie.ai, given my role?”
“Which tickets are assigned to me, and which of them should I pick up first?”
“Give me the full story behind ABC-123: what was decided, by whom, and what is still open.”
“How is the current sprint going: what is done, what is in progress and what is at risk?”
“Is there a branch or pull request for ABC-123 yet, and what state is it in?”
“Find products matching "wall plug 8 mm" and show their price and stock.”

Developer

Creates tickets and works with code: pull requests, files, designs and the central review.

Can propose: Create ticket, Add comment, Move ticket, Update ticket fields, Create sub-task, Link tickets, Contact Gunnie.

Questions to try

“What can you do for me with Gunnie.ai, given my role?”
“Which tickets are assigned to me, and which of them should I pick up first?”
“Give me the full story behind ABC-123: what was decided, by whom, and what is still open.”
“How is the current sprint going: what is done, what is in progress and what is at risk?”
“Is there a branch or pull request for ABC-123 yet, and what state is it in?”
“Find products matching "wall plug 8 mm" and show their price and stock.”

Admin

Everything, and manages members, systems and skills.

Can propose: Set review status, Create ticket, Add comment, Move ticket, Update ticket fields, Create sub-task, Link tickets, Contact Gunnie.

Questions to try

“What can you do for me with Gunnie.ai, given my role?”
“Which tickets are assigned to me, and which of them should I pick up first?”
“Give me the full story behind ABC-123: what was decided, by whom, and what is still open.”
“How is the current sprint going: what is done, what is in progress and what is at risk?”
“Is there a branch or pull request for ABC-123 yet, and what state is it in?”
“Find products matching "wall plug 8 mm" and show their price and stock.”

Every tool

What each tool does, as your assistant sees it. Writes always wait for approval first.

Tool	System	Kind	What it does
Who am I `whoami`	Gunnie.ai	Read	Your account in Gunnie.ai: organisation, role, connected systems, and the tools you may use.
What can I ask `help`	Gunnie.ai	Read	What you can ask Gunnie.ai, with example questions for your role. Writes always wait for your approval.
Search products `search_products`	Magento	Read	Searches Magento products by SKU or name: price, stock, status and visibility.
Product in the PIM `pim_product`	Akeneo	Read	Products from Akeneo by SKU: family, categories, enabled, completeness per channel and the attribute values in the configured locale and channel.
Search issues `search_issues`	Issue tracker	Read	Searches issues (Jira or Linear) with JQL or free text, within the enabled projects.
Ticket context `ticket_context`	Issue tracker	Read	The full story around a ticket in one overview: ticket, comments, branches, commits, pull requests, affected Magento modules and mentioned products.
My issues `my_issues`	Issue tracker	Read	The tickets assigned to you, reported by you, or that you watch.
Sprint overview `sprint_overview`	Issue tracker	Read	The active sprint: goal, dates, progress, and the work per status and per person.
Backlog `backlog`	Issue tracker	Read	The backlog in rank order (not in an active sprint, not done), with optional filters.
Epic overview `epic_overview`	Issue tracker	Read	An epic with its child tickets, progress, and open risks: blocked, overdue or unassigned work.
Ticket history `issue_history`	Issue tracker	Read	Who changed what on a ticket and when: status moves, assignees and field changes, with time spent per status.
Release overview `release_overview`	Issue tracker	Read	Releases (fix versions): what is in each one, how far along it is, and the dates.
Recently finished `recently_resolved`	Issue tracker	Read	Tickets finished in the last days, newest first.
Dependencies `dependencies`	Issue tracker	Read	What a ticket depends on and what depends on it: links, open blockers, parent and sub-tasks.
Search Confluence `search_pages`	Confluence	Read	Searches Confluence pages in the enabled spaces, newest first.
Read Confluence page `read_page`	Confluence	Read	Reads one Confluence page from an enabled space as text.
Pull requests `list_pull_requests`	Code host	Read	Open or recently closed pull requests per repository.
Ticket code status `ticket_code_status`	Code host	Read	Where a ticket's code is: its branches, pull requests and commits, and which shared branches (test, acceptance, master, ...) already have it.
Pull request details `pr_details`	Code host	Read	One pull request: state, description, reviewers and their verdicts, comments, build results and changed files.
Pipeline status `pipeline_status`	Code host	Read	The latest pipeline runs (Bitbucket Pipelines, GitHub Actions) and build results for a branch or pull request.
Compare branches `compare_branches`	Code host	Read	What one branch has that another does not: commits, the tickets they mention, and changed files. For example acceptance against master before a release.
Search code `code_search`	Code host	Read	Searches the code of the enabled repositories for a word, name or phrase, on their main branch.
Read file `read_file`	Code host	Read	Reads a file or directory from a repository, at a branch or commit.
Code review context `pr_review_context`	Code host	Read	Everything for reviewing one pull request: description, changed files, the diff, earlier review comments, builds and analyses, affected Magento modules and the linked Jira ticket with acceptance criteria.
Start code review `start_code_review`	Gunnie review	Read	Start a code review of one pull request on the Gunnie.ai server. Posts no comments. Returns a review_id; fetch the result with code_review_result.
Code review result `code_review_result`	Gunnie review	Read	The result of a started code review: verdict, findings per file and the acceptance criteria.
Set review status `set_review_status`	Code host	Write, after approval	Sets the Gunnie.ai code review's verdict on a pull request's latest commit as a build status, for merge checks.
Design from Figma `design_context`	Figma	Read	Design values from Figma: sizes, colours, typography, spacing and text of a frame or component, to compare with the code or a page. Without a node: the pages and frames of the file.
Create ticket `create_ticket`	Issue tracker	Write, after approval	Creates a new ticket in an enabled project. The user approves it in Gunnie.ai before it is created.
Add comment `add_comment`	Issue tracker	Write, after approval	Adds a comment to a ticket. You approve it in Gunnie.ai before it is posted.
Move ticket `transition_issue`	Issue tracker	Write, after approval	Moves a ticket to another status, if the ticket's workflow allows that step. You approve it in Gunnie.ai first.
Update ticket fields `update_fields`	Issue tracker	Write, after approval	Changes labels or priority, or adds text below the description or acceptance criteria of a ticket. Nothing is overwritten; you approve it in Gunnie.ai first.
Create sub-task `create_subtask`	Issue tracker	Write, after approval	Creates a sub-task under a ticket. You approve it in Gunnie.ai before it is created.
Link tickets `link_issues`	Issue tracker	Write, after approval	Links two tickets, for example "ABC-1 blocks ABC-2" or "relates to". You approve it in Gunnie.ai first.
Contact Gunnie `contact_gunnie`	Gunnie	Write, after approval	Sends a message to the Gunnie team, with the user as sender so the reply goes to them. The user approves it in Gunnie.ai before it is sent. If it cannot be sent directly, the result has a link to a prefilled contact form for the user to send.
Action result `action_result`	Gunnie.ai	Read	Whether the user approved a write action (such as a new ticket), and what came of it. status is one of: pending (not approved yet), approved (approved and running), done (result holds what the tool returned), rejected (the user said no), expired (not approved in time), failed (error holds the reason).