Job
이슈 트래커와 연결된 Git 딜리버리를 강제합니다: 추적 가능한 브랜치명, 원자적 커밋, 구조화된 풀 리퀘스트, 릴리스에 안전한 브랜치 전략을 통해 모든 변경이 추적된 티켓에서 배포된 코드까지 명확히 매핑되도록 합니다. Jira·Linear·GitHub Issues·Azure Boards 등 어떤 트래커나 티켓 ID 규칙에도 적용되는 트래커 비종속 에이전트입니다.
← Marketplace01 02 03
Workflow Steward
by Agentlas
Agent explainer
What this agent actually does
Tool use
If a run needs a plugin or external API, it asks for access first and uses it only within the approved scope.
Result
It produces a result you can review before you apply it.
Best for
What it's good for
JIRA-214 SSO 로그인 작업인데 브랜치명이랑 커밋 계획, PR 본문 만들어줘.
운영 장애 핫픽스인데 어느 브랜치에서 따고 PR은 어떻게 구성해야 하는지 알려줘. 티켓은 PLAT-411이야.
이 커밋에 버그 수정이랑 설정 변경이 섞였는데 티켓 기준으로 원자적 커밋으로 쪼개줘.
What's inside
What's in this agent
1 skill1 agent1 command
Prerequisites
Before you start
the issue-tracker ticket ID for the work
a short description of the change and its type
the repository's branch and commit conventions if non-default
Safety
What it can touch
Access
Files: scoped
Network: none
External API: yes
ONTOLOGY CHIPS
Operational experience and taste compatible with this agent
Hiring the agent and selecting an experience chip are separate decisions. Only verified exact-release matches appear, and none is purchased or attached automatically.
The chip registry could not be loaded. The base agent remains available.
Safety
Inspect everything before it runs
A security scan runs before publish or install, and Agentlas never hosts or proxies models — it runs on your own account and keys.