// Extract requirement details from a URL (Aone workitem, GitLab Code Review, etc.) using MCP tools. Use when the user provides a link to a requirement or review system.
Automated acceptance workflow for Terraform Provider resource releases. Supports two modes - Aone-driven (from workitem link) and local-branch (already on feature branch). Covers code review, acceptance testing, fixing failures, and CI checks.
Code review SOP for Terraform Provider resource changes. Covers delete implementation, code-doc consistency, conditional logic documentation, doc quality, test quality, and common bug patterns. Used standalone or referenced by provider-resource-acceptance.
Fix documentation issues in Terraform Provider resources. Covers attribute value corrections, description updates, example fixes, and documentation consistency checks.
Add new attributes to an existing Terraform Provider resource. Covers the full workflow from code changes (Schema/Create/Read/Update), testing, documentation, to submitting a PR.
| name | link-info-extractor |
| description | Extract requirement details from a URL (Aone workitem, GitLab Code Review, etc.) using MCP tools. Use when the user provides a link to a requirement or review system. |
| metadata | {"version":"2.0.0","domain":"requirements","triggers":"aone link, workitem, code review, codereview, requirement url, extract from link"} |
When a user provides a URL pointing to a requirement or review system, use this skill to fetch and extract structured information from that link.
| Source | URL Pattern | Parameters to Extract |
|---|---|---|
| Aone Workitem | https://project.aone.alibaba-inc.com/v2/project/<projectId>/req/<workitemId> | projectId, workitemId |
| GitLab Code Review | https://code.alibaba-inc.com/<group>/<project>/codereview/<reviewId> | group, project, reviewId |
Match the URL against known patterns above to determine the source type.
coop_query_workitem_detail(workitemId) to get the workitem description, title, and statuscoop_get_workitem_comments(workitemId) to get all commentsNote: The MCP tool name prefix (e.g.,
coop_) may vary across different app registrations, but the tool name suffix (query_workitem_detail,get_workitem_comments) stays the same. Always match by suffix.
Use the alibaba_code MCP to fetch Code Review information:
Note: The MCP name prefix may vary across different app registrations, but the underlying tool names stay the same. Always match by suffix.
From the fetched information, extract a structured technical spec. Focus on:
Attribute definitions
snake_case naming)API mapping
requestPath — parameter name for Create/Update API calls (typically PascalCase)responsePath — field name in Read API responseConstraints
Return structured requirement info:
## Requirement Summary
**Source**: [<source description>](<url>)
**Title**: <title>
### New Attributes
| Attribute | Type | Required | ForceNew | Computed | Description |
|-----------|------|----------|----------|----------|-------------|
| <name> | <type> | <Y/N> | <Y/N> | <Y/N> | <description> |
### API Mapping
- **Create**: `<API name>` — request path: `<requestPath>`
- **Read**: `<API name>` — response path: `<responsePath>`
- **Update**: `<API name>` — request path: `<requestPath>`
### Constraints
- <constraint 1>
- <constraint 2>
- ...