How I automated documentation updates with Cursor and GitHub Actions

1
### AI & Developer Tools
2

3
- [Post title](https://example.com/blog/post-slug): One-sentence description.

1
name: Update AI Index Files
2

3
on:
4
  push:
5
    branches:
6
      - master
7
    paths:
8
      - 'src/content/posts/**/*.md'
9
  workflow_dispatch:
10

11
permissions:
12
  contents: write
13

14
jobs:
15
  update-ai-index:
16
    runs-on: ubuntu-latest
17
    steps:
18
      - name: Checkout repository
19
        uses: actions/checkout@v4
20
        with:
21
          fetch-depth: 0
22

23
      - name: Install Cursor CLI
24
        run: |
25
          curl https://cursor.com/install -fsS | bash
26
          echo "$HOME/.cursor/bin" >> $GITHUB_PATH
27

28
      - name: Configure git
29
        run: |
30
          git config user.name "Cursor Agent"
31
          git config user.email "cursoragent@cursor.com"
32

33
      - name: Update AI index files
34
        env:
35
          MODEL: sonnet-4.5
36
          CURSOR_API_KEY: ${{ secrets.CURSOR_API_KEY }}
37
        run: |
38
          agent -p "You are updating AI index files for a blog.
39

40
          # Context
41
          A blog post was added, modified, or deleted in src/content/posts/.
42

43
          # Files to Update
44
          1. public/llms.txt - Concise AI index with post titles and descriptions
45
          2. public/llms-full.txt - Comprehensive AI index with full article summaries
46

47
          # Scope
48
          First identify which post files changed in this run.
49
          - For push events, use the git range `${{ github.event.before }}`..`${{ github.sha }}`
50
          - If `${{ github.event.before }}` is empty or all zeros, use `HEAD^..HEAD`
51
          - Only inspect changed markdown files inside src/content/posts/
52
          - Do not read all posts unless you absolutely need a single adjacent entry to place a changed item in the correct sorted position
53

54
          # Instructions
55
          1. Identify the changed post files for this run from git diff.
56
          2. Read only:
57
             - the changed post files that still exist
58
             - public/llms.txt
59
             - public/llms-full.txt
60
          3. Use each changed post's frontmatter as the source of truth for title, description, category, tags, slug, and published date (`pubDate`).
61
          4. Update only the matching entries or article blocks for the changed posts:
62
             - Add entries for newly added posts
63
             - Remove entries for deleted posts
64
             - Update entries only when the changed post's title, description, slug, category, tags, pubDate, or article meaning changed materially
65
          5. If a changed post does not require an AI index update, make no edit for that post.
66
          6. Preserve every unrelated entry and article block exactly as written. Do not normalize wording, headings, bullet style, or formatting across existing posts.
67
          7. Keep the author info, navigation, and site information sections exactly unchanged.
68
          8. For existing posts, edit in place rather than regenerating nearby content.
69
          9. In public/llms.txt, move only the affected entry if a changed post's category or pubDate requires a different sorted position.
70
          10. In public/llms-full.txt, move only the affected article block if a changed post's pubDate requires a different sorted position.
71
          11. Maintain the current format and structure already used in each file.
72
          12. Only modify public/llms.txt and public/llms-full.txt.
73
          13. Do not modify any other files.
74

75
          # Format for llms.txt entries
76
          - [Post Title](https://theodoroskokosioulis.com/blog/slug): Brief description.
77

78
          # Format for llms-full.txt sections
79
          - For existing posts, preserve the current section structure of that post's block.
80
          - For brand new posts, use:
81
            ## Article: Post Title
82
            **URL:** https://theodoroskokosioulis.com/blog/slug
83
            **Published:** Month Day, Year from the post frontmatter pubDate
84
            **Category:** Category Name
85
            **Tags:** Tag1, Tag2
86
            ### Summary
87
            Description from frontmatter.
88
            ### Key Points
89
            - Extract 3-5 main takeaways from the article content
90

91
          # Important
92
          - Do not rewrite unrelated posts just to make the file more uniform
93
          - Do not touch a post block or list item if that post did not change in this run
94
          - Preserve the author info, site information, and navigation sections exactly
95
          " --force --model "$MODEL" --output-format=text
96

97
      - name: Check for changes
98
        id: git-check
99
        run: |
100
          git add public/llms.txt public/llms-full.txt
101
          if git diff --staged --quiet; then
102
            echo "changes=false" >> $GITHUB_OUTPUT
103
          else
104
            echo "changes=true" >> $GITHUB_OUTPUT
105
          fi
106

107
      - name: Commit and push changes
108
        if: steps.git-check.outputs.changes == 'true'
109
        run: |
110
          git commit -m "chore: update AI index files for blog changes"
111
          git push