Agent skill
ticket-comment
Add a structured comment to a ticket
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/ticket-comment-daemn256-workspace-repo-templ
SKILL.md
Ticket Comment
Uses Orchestrator for ticket lifecycle. Add a structured comment to an existing ticket for progress updates, status changes, or decision records.
Prerequisites: Ticket number, comment content or context for composing one
Comment Types
| Type | When to Use | Format |
|---|---|---|
| Progress | Work milestone reached | Status summary + what's next |
| Decision | Design choice made during work | Decision + rationale + alternatives |
| Blocker | Work blocked by external dependency | What's blocked + what can unblock |
| Completion | Work finished, ready for next phase | Summary of what was done |
Steps
- Determine the comment type based on context
- Compose the comment using the appropriate format
- Present the draft for approval
⛔ CHECKPOINT
STOP. Await approval of the comment.
- Execute the forge's comment operation on the issue
Output
## Context Anchors
- **Issue:** #<number> - <title>
## Commented
- **Type:** <comment type>
## Next Step
Comment added.
**Approval Required:** No
Error Handling
| Error | Recovery |
|---|---|
| Issue not found | Verify the issue number |
| Comment unclear | Ask for clarification |
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?