factory-complete-issue
Mark a GitHub issue as done and update its status labels
60
70%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./mastracode/factory/factory-skills/factory-complete-issue/SKILL.mdFactory Complete Issue
Mark the GitHub issue behind a completed Factory work item as done and update its status labels.
Parse the issue URL or number from $ARGUMENTS, then read its current state and labels. Remove any of these labels that are present:
status: needs triagestatus: auto-triagedstatus: needs approval
Use gh issue edit to remove the listed triage labels. If the issue is open, add status: pending-close when it is not already present and post this comment unless the issue already has it:
This issue has now been marked as done.
If the issue is already closed, do not add status: pending-close or post the comment. Do not modify any other labels or issue fields.
Do not close, reopen, or assign the issue, and do not request another Factory transition.
- Repository
- mastra-ai/mastra
- Commit
3b0d190
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.