link_commit
writeFeature Specs
Link a git commit SHA to a spec and task for traceability.
Connected surface
This tool and the Specs dashboard page are two surfaces over the same data. The dashboard is where you view and curate it;
link_commit is how your AI can stamp each commit onto the spec and task it implements. How surfaces connect →Write tool
Mutates Rampify state, triggers background work, or calls a paid external API. Most clients ask for confirmation before invoking.
Parameters
| Parameter | Type | Description | |
|---|---|---|---|
| spec_id | string | required | UUID of the feature spec to link the commit to |
| commit_sha | string | required | Git commit SHA (from `git rev-parse HEAD`) |
| task_id | string | optional | UUID of a specific task to link the commit to. Always pass when one task drove the commit. |
| repo_url | string | optional | Repository HTTPS URL (e.g., "https://github.com/owner/repo") |
| commit_message | string | optional | Full commit message body. When passed, Task: and Spec: trailers are parsed to auto-populate task_id and validate spec_id. |
| domain | string | optional | Site domain |
| project_id | string | optional | Project UUID |
Related tools
create_feature_specwriteCreate and save a feature specificationget_feature_specreadFetch one spec by UUID with full nested detaillist_feature_specsreadFind specs by search/status/priority/tags/etc; supports summary_only for fast scansupdate_feature_specwriteUpdate spec body fields: title, description, status, priority, tags, etc.