Every skill your team needs. One conversation away.
dev-agents ships with six built-in skills that work the moment you deploy. Ask questions in Slack. Get code-level answers. No training, no configuration, no new tools.
Free to start. Deploy in minutes.
Built-in skills for every dev team need.
Ready on day one. Build custom skills for anything else.
Code Research
Explore the codebase through conversation.
"How does the authentication flow work?"
Code Review
Automated review on every PR. Bugs, security, style.
"Review PR #342 for security issues"
Test Plans
Generate test plans from PRs, tickets, or user stories.
"Create a test plan for this Jira ticket"
Release Notes
Auto-generated changelogs from commits and PRs.
"Generate release notes for v2.4"
Story Refinement
Enhance user stories with acceptance criteria and edge cases.
"Refine this user story with edge cases"
Log & Issue Analysis
Identify root causes from error logs and support tickets.
"Why is this customer getting a 500 error?"
Built-in skills ship ready. On Pro and Power, use the Skill Builder to create custom skills for your workflows.
Ask your codebase anything.
Explore architecture, trace logic, and understand decisions - through conversation in Slack.
New team members need context. Product owners need to understand impact. Support needs to trace customer issues. DevOps needs to know how systems connect.
The Code Research skill lets anyone on your team ask questions about the codebase and get answers in plain language - right in Slack or Teams. No IDE required. No developer interrupted.
Key Benefits
- Anyone on the team can explore the codebase
- Answers in plain language, not code dumps
- No IDE access or technical setup required
Used by: Developers, Product Owners, DevOps, Support, New Hires
Example Prompts
"How does the authentication flow work?"
"Which services call the payment API?"
"What changed in the billing module since January?"
"Where is the retry logic for failed webhooks?"
Catch issues before they ship.
Automated review on every pull request. Bugs, security gaps, style violations - flagged before human review begins.
Every PR deserves a review. But reviewers are busy, context-switching is expensive, and some issues slip through.
The Code Review skill runs automatically on every pull request. It checks for bugs, security vulnerabilities, style inconsistencies, and deviation from your team's patterns. By the time a human reviewer opens the PR, the obvious issues are already flagged.
Key Benefits
- Consistent standards across every PR, every reviewer
- Security and bug checks that never skip a day
- Human reviewers spend time on architecture, not syntax
Used by: Developers, Tech Leads, Security Engineers
Example Prompts
"Review PR #342 for security issues"
"What are the risks in this change?"
"Does this PR follow our API naming conventions?"
Know exactly what to test.
Generate test plans from pull requests, tickets, or user stories - so QA never has to guess.
When a PR lands, someone needs to figure out what to test. Usually that means reading the code, tracing the changes, and hoping nothing gets missed.
The Test Plans skill reads the code changes and generates a structured test plan: what to test, what edge cases to cover, and what areas might break. QA gets a starting point in minutes instead of hours.
Key Benefits
- Test coverage that actually matches the code change
- Edge cases surfaced before they become bugs in production
- QA teams start testing faster, with more confidence
Used by: QA Engineers, QA Leads, Product Owners, Developers
Example Prompts
"Create a test plan for this Jira ticket"
"What should I test for PR #218?"
"What edge cases should we cover for the new checkout flow?"
Ship changelogs without the busywork.
Auto-generated release notes from commits and pull requests. Ready to share with your team or your customers.
Release day arrives. Someone scrambles to compile what changed, cross-reference PRs with tickets, and write something readable. It takes hours. It's always behind.
The Release Notes skill generates changelogs directly from your commits and PRs. Internal format for the team. Customer-facing format for the product update. Both created from a single prompt.
Key Benefits
- Release notes that are accurate because they come from the code
- Two formats: internal (technical) and external (customer-facing)
- No more scrambling on release day
Used by: Product Owners, Engineering Managers, Developer Relations
Example Prompts
"Generate release notes for v2.4"
"What shipped in the last two weeks?"
"Create a customer-facing changelog for this sprint"
Better stories before the sprint starts.
Enhance user stories with acceptance criteria, edge cases, and technical considerations - before refinement even begins.
Refinement meetings eat time. Half the session is spent discovering what's missing from the story - unclear acceptance criteria, forgotten edge cases, dependencies nobody mentioned.
The Story Refinement skill analyzes user stories and adds what's missing: acceptance criteria, edge cases, technical considerations, and questions for the team. Stories arrive at refinement already detailed.
Key Benefits
- Stories that arrive at refinement already detailed
- Edge cases caught before development starts, not after
- Shorter refinement meetings, fewer mid-sprint surprises
Used by: Product Owners, Scrum Masters, Tech Leads, Developers
Example Prompts
"Refine this user story with edge cases"
"Add acceptance criteria to JIRA-1234"
"What technical dependencies does this story have?"
Find the root cause, not just the symptom.
Analyze error logs, stack traces, and support tickets to identify what went wrong and why.
A customer reports an error. Support opens the ticket. Someone needs to trace the issue through logs, correlate it with recent changes, and figure out what broke.
The Log & Issue Analysis skill reads error logs, stack traces, and support tickets - then traces the issue through your codebase to identify the root cause. It suggests what went wrong, what code is involved, and where to start fixing.
Key Benefits
- Root cause analysis that starts from the code, not just the logs
- Support and DevOps get answers without waiting for a developer
- Incident response that connects symptoms to code changes
Used by: DevOps, Support Engineers, On-Call Developers, SREs
Example Prompts
"Why is this customer getting a 500 error?"
"Analyze these error logs and find the root cause"
"What changed recently that could cause this timeout?"
Your workflows. Your skills.
Build custom skills for any workflow your team needs. No code required.
Built-in skills cover the most common dev team needs. But every team has workflows that are unique - migration checklists, dependency audits, architecture decision records, API documentation, sprint retrospectives.
On Pro and Power plans, the Skill Builder lets you create custom skills using plain language. Define what the skill does, what context it needs, and how it should respond. Your team uses it the same way - just ask in Slack.
Examples teams have built
- + Migration assistant for legacy code transitions
- + API documentation generator from code comments
- + Dependency update reviewer with risk assessment
- + Security vulnerability scanner for specific frameworks
- + Sprint retrospective summarizer from Slack threads
One agent. Your whole team.
Every role gets code-level answers - without learning to code.
Developers
Stop context-switching to answer questions. The agent handles code research, review prep, and documentation so you can stay in flow.
"How does the retry logic work in the payment service?"
QA Engineers
Generate test plans from PRs and stories. Get edge cases surfaced before you start testing.
"Create a test plan for PR #218"
Product Owners
Research features, trace changes, and refine stories - without waiting for a developer to free up.
"What's the impact of removing the legacy billing module?"
DevOps & SREs
Analyze incidents, trace errors, and understand deployment changes through conversation.
"What changed in the last deployment that could cause this timeout?"
Support Engineers
Trace customer issues to code. Get technical context for bug reports without escalating to engineering.
"Why is customer #4521 getting a 403 on the dashboard?"
Engineering Managers
Generate release notes, track what shipped, and get visibility into code changes without reading every PR.
"What did the team ship this week?"
Used daily by a 50-person engineering team.
"Product owners, DevOps, even customer care use the agent for code research and test planning. The ROI is roughly 10:1. What used to require interrupting a developer now happens in Slack."
CTO
Medical SaaS Company - 50 users, daily multi-use across the organization
Deploy your AI agent today.
Six built-in skills. Your whole team. Running in minutes.