Skip to content

For the complete documentation index, see llms.txt.

August 2026

New Features:

  • Re-review GitHub PRs as new commits land: Promptless re-reviews an open pull request on each push, so its suggestions match the latest code. Turn it on for specific repositories in a GitHub PR trigger. See Re-review open PRs on every push.
  • Start Promptless from a Jira issue: Assign, label, or mention Promptless on an issue, or trigger on a project, label, or status. Promptless replies on the issue with the documentation PR linked, so the team follows the docs work where it tracks the rest. See Jira triggers.
  • Request docs from GitLab comments: Mention @promptless in a merge-request comment to get docs for it, even in a project your triggers don’t watch. A 👀 reaction confirms Promptless saw the mention, and a comment on a merge request Promptless opened revises that suggestion. See Request documentation via merge-request comments.
  • Check sources on GitLab merge requests: Promptless posts a suggestion’s citations as discussion threads on its GitLab merge request, as on GitHub. Reviewers check each claim’s source where they review the diff. See Check sources on the docs PR.
  • Run documentation checks on a schedule: Give Promptless standing instructions to run on a repeating schedule in your timezone. For example, check every Monday morning that the changelog and release-notes page still agree. See Schedule triggers.
  • Review every screenshot change in one place: The Screenshot Updates tab gathers screenshots from every open suggestion into one gallery, grouped by doc collection. Catch screenshot changes that are easy to miss one suggestion at a time. See Review screenshot changes.
  • Start documentation tasks from your editor over MCP: Start and track documentation tasks from an MCP client such as Claude Code or Cursor. Each teammate connects with their own sign-in, with no API key to create or share. See MCP triggers.
  • Triage your suggestion backlog from your editor: Editors that support the draft MCP Skills extension can load a backlog-triage skill. The skill gives each suggestion one outcome, and suggestion search filters by label to pull a queue such as every P0 suggestion. See Workflow skills.
  • Connect your tools over the HTTP API: Submit documentation tasks, follow suggestion changes, and list doc collections from any HTTP client with an API key. A retried submission doesn’t create a duplicate task, so scripts can retry safely. See API triggers.
  • Give each integration its own API key: Name each key for what uses it, and create or revoke it without affecting your other keys. Rotate a leaked key or retire an integration without breaking the rest. See Manage and rotate keys.

Improvements:

  • Review and revise suggestions from your editor: Ask Promptless to revise a suggestion and it updates the same docs PR. Label, assign, rename, open, or close a suggestion yourself, and connect from more clients, such as VS Code and Codex CLI. See MCP triggers.
  • Search suggestions by keyword from your editor: Searching suggestions over MCP now takes a search term and returns only the suggestions that match it. See search_suggestions.
  • See which checks failed: A failed check on a docs PR appears in its suggestion’s timeline as a “CI failed” event naming the checks. Tell machine-reported CI status apart from feedback a person left.
  • Follow Promptless’s research in order: A trigger’s research breakdown lists Knowledge Base reads in the order the agent read them. Research delegated to a subagent appears as its own labeled branch, so you can see what each one looked into. See See what Promptless researched.
  • Backfill first-approval GitHub PR triggers: Catch up on pull requests first approved within the backfill window, even ones opened earlier. See Backfill suggestions.
  • See why a trigger made no change: Completed trigger cards show the agent’s response, which often explains why a run produced no suggestion. Open the research breakdown in place on the card. See Follow what a trigger did.

Bug Fixes:

  • Review and apply image changes: Image changes show as a side-by-side before-and-after diff. Image-only suggestions show their real status, so you can apply and publish them like any other, and rejecting an image restores its original. See Check how changes render.
← OlderJuly 2026