cd-adjust

Adjust Ticket

Apply this adjustment: $ARGUMENTS

The argument format is <issue-number> <feedback text> — the first whitespace-separated token is the issue number, the rest is the feedback.

Process

1. Parse arguments. Split $ARGUMENTS into <issue-number> and <feedback>.

2. Load context. Call cd_get_ticket with the parsed issue number. Read the refinement artifact and any prior adjustments.

3. Check out the ticket branch. Discover the branch name via Bash rather than re-deriving the slug (the title may have changed since implementation):

   git branch --list "cd/<issue-number>-*" --format="%(refname:short)" | head -n1
   

   Check out the result. If the command returns empty, the ticket has no implementation branch yet — stop and tell the user.

4. Make the change. Apply the feedback. Keep edits minimal and focused.

5. Commit. Run via Bash:

   git commit -am "[cd#<issue-number>] adjust: <short summary of feedback>"
   

6. Push. Run git push via Bash. This updates the open PR.

7. Write the adjustment artifact. Call cd_write_artifact with:

   • issue_number: the parsed issue number

   • type: adjustment

   • content:

     # Adjustment for #<n>
     
     ## Requested change
     
     <feedback verbatim>
     
     ## What changed
     
     <files and summary>
     
     ## Rationale
     
     <why this approach>
     

Rules

• Do not transition state. /cd-adjust leaves the ticket in whatever state it was in.
• Do not modify files outside the adjustment's scope.
• If the branch does not exist, the ticket is not in-progress — stop and tell the user.