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>
3.7 KiB
Get Current Time
What it is
A block that provides the current time.
What it does
This block outputs the current time in hours, minutes, and seconds.
How it works
When triggered, the block retrieves the current system time and formats it as a string in the HH:MM:SS format.
Inputs
| Input | Description |
|---|---|
| trigger | A string input that activates the block. The content of this input doesn't affect the output. |
Outputs
| Output | Description |
|---|---|
| time | A string representing the current time in the format HH:MM:SS (e.g., "14:30:45"). |
Possible use case
This block could be used in a chatbot that needs to provide the current time to users when asked.
Get Current Date
What it is
A block that provides the current date, with an optional offset.
What it does
This block outputs the current date or a date offset from the current date by a specified number of days.
How it works
When triggered, the block retrieves the current system date. If an offset is provided, it calculates a new date by subtracting the offset number of days from the current date. The resulting date is then formatted as a string in the YYYY-MM-DD format.
Inputs
| Input | Description |
|---|---|
| trigger | A string input that activates the block. The content of this input doesn't affect the output. |
| offset | An integer or string representing the number of days to subtract from the current date. If not provided or invalid, it defaults to 0. |
Outputs
| Output | Description |
|---|---|
| date | A string representing the date in the format YYYY-MM-DD (e.g., "2023-05-15"). |
Possible use case
This block could be used in a scheduling application to calculate and display dates for upcoming events or deadlines.
Get Current Date and Time
What it is
A block that provides both the current date and time.
What it does
This block outputs the current date and time combined into a single string.
How it works
When triggered, the block retrieves the current system date and time, then formats them together as a string in the YYYY-MM-DD HH:MM:SS format.
Inputs
| Input | Description |
|---|---|
| trigger | A string input that activates the block. The content of this input doesn't affect the output. |
Outputs
| Output | Description |
|---|---|
| date_time | A string representing the current date and time in the format YYYY-MM-DD HH:MM:SS (e.g., "2023-05-15 14:30:45"). |
Possible use case
This block could be used in a logging system to timestamp events with both date and time information.
Countdown Timer
What it is
A block that acts as a countdown timer, triggering after a specified duration.
What it does
This block waits for a specified amount of time and then outputs a message.
How it works
The block takes input for the duration in days, hours, minutes, and seconds. It calculates the total wait time in seconds, pauses execution for that duration, and then outputs the specified message.
Inputs
| Input | Description | Default |
|---|---|---|
| input_message | The message to be output when the timer finishes. | "timer finished" |
| seconds | The number of seconds to wait. | 0 |
| minutes | The number of minutes to wait. | 0 |
| hours | The number of hours to wait. | 0 |
| days | The number of days to wait. | 0 |
Outputs
| Output | Description |
|---|---|
| output_message | The message specified in the input_message, output after the timer completes. |
Possible use case
This block could be used in a reminder application to trigger notifications after a set amount of time, or in a cooking app to notify users when a recipe step is complete.