Agent skill
ticket-body
Update a ticket's description or body content.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/ticket-body
SKILL.md
Ticket Body
The Orchestrator drives this workflow. Update the body/description of an existing ticket while preserving its structure.
Prerequisites: Ticket number, knowledge of what needs to change.
Steps
- Read the current issue body via the forge's read operation
- Identify the section(s) to update
- Compose the updated body, preserving sections that shouldn't change
- Present the changes for approval — show what's changing and the full updated body
⛔ CHECKPOINT
STOP. Await approval of the body changes.
- Write the updated body to
.tmp/scratch/issue-body.md - Execute the forge's issue update operation with the new body
Output
## Context Anchors
- **Issue:** #<number> - <title>
## Updated
- **Sections changed:** <list of sections modified>
## Next Step
Ticket body updated.
**Approval Required:** No
Error Handling
| Error | Recovery |
|---|---|
| Issue not found | Verify the issue number |
| Section not found | Show available sections, ask which to update |
| Body format corrupted | Present the full body for manual review |
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
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.
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.
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.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
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?