GitLab Issue Creation
Create GitLab issues from app feedback and operational events in the chosen project.
What it adds
A server-side path from an in-app report or system event to an issue in a configured GitLab project, on hosted or self-managed GitLab.
What your agent is told to do
5
What your agent is told to do
5-
1
Make the GitLab host part of the connection, not a constant. Self-managed installations live on customer-controlled domains, so validate the host, its reachability, and the credential's scope at setup, and store both server-side only.
-
2
Let an administrator map the destination project along with labels, milestone, assignee, and whether the issue is created confidential. Default to confidential when the report may contain customer data, and make that default explicit rather than implied.
-
3
Compose the issue on the server from the originating record, a deep link back into the app, and the acting user's identity, redacting credentials and personal data from any attached log before it leaves the app.
-
4
Key each submission by the originating record so a retry after a timeout finds the existing issue instead of creating a second one, and store the returned issue reference for later status reconciliation.
-
5
GitHub Issue Creation, Linear Issue Creation, Jira Ticket Creation, Trello Card Creation, and Asana Task Creation are siblings. The capture, redaction, deduplication, and reference storage belong to a single shared path; this brief owns only the GitLab host handling, field mapping, and error translation.
Edge cases it handles
8
Edge cases it handles
8- A self-managed host may sit behind a VPN, present an internal certificate, or run a version with different capabilities. Verify connectivity at setup, fail with a clear administrator-facing message, and do not assume the hosted service's behaviour applies.
- Labels, milestones, assignees, and the confidentiality flag must be selected from what the connected account can see in that project, and re-validated on use. A milestone closed or a label deleted since setup must not abort the submission; drop the unknown attribute, create the issue, and note what was dropped.
- Repeated submissions of the same report must converge on one issue. Fingerprint on the originating record or the error signature and comment on the existing issue rather than opening another.
- The project path, the host, and the token must never appear in client-side code, in an error message shown to a user, or in the issue body. A reporting user typically has no GitLab account at all and must not learn where private projects live.
- Projects get moved, renamed, transferred, or archived. Detect the redirect or the archived state, surface a configuration error to an administrator, and hold the queued reports rather than discarding them.
- Tokens expire and get revoked. Treat an authentication failure differently from a transient error: stop retrying, keep the submissions queued, and prompt an administrator to reconnect.
- Rate limits on hosted GitLab and on constrained self-managed instances require exponential backoff with jitter and a bounded retry count.
- When the GitLab instance is unreachable, accept the report in the app and create the issue later. The user sees their feedback recorded, not another organisation's outage.
Definition of done
9
Definition of done
9- The GitLab host is configurable and validated at setup, covering hosted and self-managed installations.
- An administrator chooses the project, labels, milestone, assignee, and confidentiality, selected from what the connection can see.
- Duplicate or retried submissions resolve to the existing issue rather than a new one.
- Host, project path, and token never appear in client-side code, user-facing errors, or issue content.
- A moved or archived project raises an administrator-facing configuration error while queued reports are preserved.
- Authentication failures stop retries and prompt a reconnection instead of dropping submissions.
- An unreachable instance still records the report, which is created once the host returns.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
AI Cost Budgets
AI Cost Budgets
Cap what AI features are allowed to spend before the bill arrives.
What it does
Monetary spending limits on AI work, scoped by workspace, feature, and time period, enforced before a run starts.
How it works
- 1 Find every place the app calls a model and route all of them through one accounting point that records estimated and actual spend against a scope. A budget that only covers the chat feature is not a budget.
- 2 Estimate the cost of a run from the size of its input before dispatching it, and refuse anything that would exceed the remaining budget on its own.
- 3 Reserve the estimate against the budget when the run starts, then reconcile to the real usage figures when it finishes, releasing whatever was over-reserved.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/ai-cost-budgets
Multi-Model Routing
Multi-Model Routing
Send each AI request to the right model using rules you can read and test.
What it does
A deterministic routing layer that picks a model per request from task type, context size, latency budget, and data sensitivity.
How it works
- 1 Express routing as explicit, ordered rules over inputs the app can measure: task type, estimated context size, latency budget, and the sensitivity classification of the data involved. A rule set that can be read line by line can be reviewed and tested.
- 2 Make routing deterministic. The same inputs must always produce the same route, so a bad output can be reproduced and a rule change can be evaluated. Randomised or load-based selection turns every incident into guesswork.
- 3 Classify data before routing and refuse to route restricted content to any destination not approved for it. This check is a hard block, not a preference, and it must run before the request is assembled.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/multi-model-routing
SEO Setup
SEO Setup
Make your app findable — titles, meta, Open Graph, sitemap, robots.
What it does
The baseline SEO and social-preview setup every public app should have, and most skip.
How it works
- 1 Give every public page a unique, descriptive title and meta description. Find the app's layout and add a mechanism for each page to set them.
- 2 Add Open Graph and Twitter Card tags so shared links render a preview instead of a bare URL.
- 3 Generate a sitemap.xml covering every public, indexable page, and a robots.txt pointing at it.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/seo-setup
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.