# Docs Agent — AI-powered documentation assistant

import { Aside, Card, CardGrid, LinkCard } from '@astrojs/starlight/components';

<Aside type="note" title="Beta">
  Docs Agent is in beta. Contact support@ekline.io to request access.
</Aside>

### See Docs Agent in action

<div style={{padding:'56.25% 0 0 0', position:'relative'}}>
  <iframe
    src="https://www.youtube.com/embed/xn3cq_dfQVY"
    frameBorder="0"
    allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
    referrerPolicy="strict-origin-when-cross-origin"
    allowFullScreen
    style={{position:'absolute', top:0, left:0, width:'100%', height:'100%'}}
    title="Docs Agent Demo"
  />
</div>

Docs Agent is an AI assistant that helps you create documentation from your codebase, keep docs in sync when code changes, and improve existing content.

## What you can do

<CardGrid>
  <Card title="Generate new docs" icon="document">
    Create README files, API references, and guides from your code, videos, or external sources.
  </Card>
  <Card title="Update from tickets" icon="pencil">
    Reference a Linear or Jira ticket and the agent updates relevant documentation automatically.
  </Card>
  <Card title="Review and improve" icon="approve-check">
    Get feedback on clarity, completeness, accuracy, and consistency.
  </Card>
  <Card title="Pull from integrations" icon="puzzle">
    Reference Slack threads, Notion pages, Confluence docs, or Google Docs in your prompts.
  </Card>
  <Card title="Trigger from GitHub" icon="github">
    Mention `@ekline-ai` on any pull request comment to generate docs linked to the PR context.
  </Card>
</CardGrid>

## How it works

1. **Describe what you need** — Tell the agent what documentation to create or update.
2. **Agent analyzes your sources** — It reads your codebase, tickets, or linked content.
3. **Review the output** — Edit the generated content in the built-in editor.
4. **Create a pull request** — Publish changes through your normal review process.

The agent learns from your existing documentation to match your style, terminology, and structure.

## What you can create

- **README files** — From repository structure and code.
- **API references** — From function signatures, types, and comments.
- **How-to guides** — From support threads or internal knowledge.
- **Release notes** — From completed tickets in a milestone.
- **Getting started guides** — For new users or contributors.
- **Troubleshooting docs** — From incident resolutions or FAQs.

## Next steps

<CardGrid>
  <LinkCard
    title="Getting started"
    description="Create your first document in 5 minutes"
    href="/agent/getting-started/"
  />
  <LinkCard
    title="Integrations"
    description="Connect Slack, Notion, Linear, and more"
    href="/agent/integrations/"
  />
  <LinkCard
    title="Enforce style guides"
    description="Catch quality issues automatically with Docs Reviewer"
    href="/reviewer/quickstart/"
  />
</CardGrid>