2026-05-22

GitLink

I've been puzzled for a while: why use an Agent to label PRs? Labeling PRs could be done simply by checking the paths of modified files.

Today it suddenly hit me: the challenge is about Issues, not PRs! Even though I wrote "PR/Issue" in yesterday's notes, the main task yesterday was the contributor system, which involved labeling PRs, so I had PRs on my mind the whole time, not Issues.

Using an Agent to label Issues makes perfect sense—let the AI analyze the content of the Issue, then automatically label it and assign the responsible person.

Deployment Approach

The ideal approach would be to use the repository's CI pipeline, but GitLink's pipeline currently doesn't support triggering on "new Issue" events. Also, since this is an Agent Skill, perhaps developers are meant to deploy the Agent locally to monitor the repository's status.

Using the repository's webhook feature for real-time monitoring could be a solution. When a new Issue is created, the GitLink platform sends a POST request to the URL set by the developer.

Scheduled tasks are nothing new in Agents.