c1a1767034
- Add generate_block_docs.py script that introspects block code to
generate markdown
- Support manual content preservation via <!-- MANUAL: --> markers
- Add migrate_block_docs.py to preserve existing manual content from git
HEAD
- Add CI workflow (docs-block-sync.yml) to fail if docs drift from code
- Add Claude PR review workflow (docs-claude-review.yml) for doc changes
- Add manual LLM enhancement workflow (docs-enhance.yml)
- Add GitBook configuration (.gitbook.yaml, SUMMARY.md)
- Fix non-deterministic category ordering (categories is a set)
- Add comprehensive test suite (32 tests)
- Generate docs for 444 blocks with 66 preserved manual sections
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
<!-- Clearly explain the need for these changes: -->
### Changes 🏗️
<!-- Concisely describe all of the changes made in this pull request:
-->
### Checklist 📋
#### For code changes:
- [x] I have clearly listed my changes in the PR description
- [x] I have made a test plan
- [x] I have tested my changes according to the test plan:
<!-- Put your test plan here: -->
- [x] Extensively test code generation for the docs pages
<!-- CURSOR_SUMMARY -->
---
> [!NOTE]
> Introduces an automated documentation pipeline for blocks and
integrates it into CI.
>
> - Adds `scripts/generate_block_docs.py` (+ tests) to introspect blocks
and generate `docs/integrations/**`, preserving `<!-- MANUAL: -->`
sections
> - New CI workflows: **docs-block-sync** (fails if docs drift),
**docs-claude-review** (AI review for block/docs PRs), and
**docs-enhance** (optional LLM improvements)
> - Updates existing Claude workflows to use `CLAUDE_CODE_OAUTH_TOKEN`
instead of `ANTHROPIC_API_KEY`
> - Improves numerous block descriptions/typos and links across backend
blocks to standardize docs output
> - Commits initial generated docs including
`docs/integrations/README.md` and many provider/category pages
>
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
631e53e0f6. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
---------
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
2.6 KiB
Twitter List Follows
Blocks for following and unfollowing Twitter/X lists.
Twitter Follow List
What it is
This block follows a specified Twitter list for the authenticated user.
How it works
This block uses the Twitter API v2 via Tweepy to follow a Twitter List. Following a list adds it to your Lists tab and shows tweets from list members in your timeline when viewing that list.
The block authenticates using OAuth 2.0 with list write permissions and sends a POST request to add the follow relationship. Returns a success indicator confirming the list was followed.
Inputs
| Input | Description | Type | Required |
|---|---|---|---|
| list_id | The ID of the List to follow | str | Yes |
Outputs
| Output | Description | Type |
|---|---|---|
| error | Error message if the operation failed | str |
| success | Whether the follow was successful | bool |
Possible use case
Curated Content Discovery: Follow lists curated by industry experts to access filtered content streams.
Topic Monitoring: Follow lists focused on specific topics to stay informed without following individual accounts.
Research Organization: Follow competitor or industry lists to monitor activity without cluttering your main timeline.
Twitter Unfollow List
What it is
This block unfollows a specified Twitter list for the authenticated user.
How it works
This block uses the Twitter API v2 via Tweepy to unfollow a Twitter List. The list is removed from your Lists tab but remains accessible if it's public.
The block authenticates using OAuth 2.0 with list write permissions and sends a DELETE request to remove the follow relationship. Returns a success indicator confirming the list was unfollowed.
Inputs
| Input | Description | Type | Required |
|---|---|---|---|
| list_id | The ID of the List to unfollow | str | Yes |
Outputs
| Output | Description | Type |
|---|---|---|
| error | Error message if the operation failed | str |
| success | Whether the unfollow was successful | bool |
Possible use case
List Cleanup: Unfollow lists that are no longer relevant or useful to your interests.
Focus Management: Reduce information overload by unfollowing less important lists.
Account Organization: Clean up your followed lists as part of regular account maintenance.