Keep reusable repository guidance ready for future prompts
Refresh a cache of stable project instructions when the repository README changes, helping repeated calls avoid resending the same prompt content.
Trigger
GitHub Repository README Changed
Triggers when the README file in a specific repository directory changes. Monitors the README in a configurable directory and branch/tag/commit. The payload includes the current README metadata (filename, path, SHA, size, URLs), the previous and current git blob SHAs, and a list of which tracked fields changed.
Action
Prompt Caching
Tool to cache and reuse prompt content to reduce costs and latency. use after you have static prompt portions you intend to reuse across calls.
Why this helps
Repeatedly supplying the same repository guidance adds friction and can increase prompt costs and latency.
- Refresh reusable prompt content when the monitored README changes.
- Reduce repeated transmission of stable instructions across later calls.
- Keep cache content scoped to guidance you explicitly identify.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Anthropic administrator once in the Notis portal.
- 2Create an automation in Automations, then choose a name and prompt.
- 3Tell Notis which stable README guidance to cache and how to handle missing or changed content.
- 4Pick the GitHub Repository README Changed trigger and set the repository location and branch in the trigger options.
- 5Choose a report channel and test with one real README change.
Questions about this workflow
Does this cache the entire README automatically?
The prompt should specify which stable content to cache. The trigger supplies README change information, and only content actually available to Notis can be used.
Will the cache update on every repository change?
This trigger monitors a README in a configured repository directory and branch, tag, or commit. It fires when that README changes.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Anthropic administrator. A trigger fires from one place; an action lands in another.
GitHub triggers
Anthropic administrator actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Message
Tool to create a new message completion. use when you need to generate assistant text given a conversation history.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Model
Tool to retrieve details of a specific model by its id. use after confirming the model id is valid.
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
List models
Tool to list available models. use when you need to see which models are available before selection.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
Prompt Caching
Tool to cache and reuse prompt content to reduce costs and latency. use after you have static prompt portions you intend to reuse across calls.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
Connect any two apps with Notis in the middle.
GitHub and Anthropic administrator, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Anthropic administrator.