.nh
.TH "pogo" "1" "Oct 2025" "pogo/dev" "Pogo Manual"

.SH NAME
pogo-describe - Set the description for the current change


.SH SYNOPSIS
\fBpogo describe [flags]\fP


.SH DESCRIPTION
Set or modify the description for the current change.

.PP
In Pogo's workflow, you should describe your changes BEFORE you start working.
This helps you think through what you're about to do and communicate your
intentions to others. You can update the description as you work to reflect
any changes in your implementation approach.

.PP
If no description is provided via the -m flag, an editor will open where you
can write a detailed description. The description follows the Conventional
Commits format by default.

.PP
The description is crucial for understanding the history of your project and
should explain both WHAT changed and WHY it changed.

.PP
This command pushes any changes before running.


.SH OPTIONS
\fB-m\fP, \fB--description\fP=""
	Description for the change

.PP
\fB-f\fP, \fB--force\fP[=false]
	Force push even if the change is readonly

.PP
\fB-h\fP, \fB--help\fP[=false]
	help for describe


.SH OPTIONS INHERITED FROM PARENT COMMANDS
\fB--time\fP[=false]
	Measure command execution time

.PP
\fB-v\fP, \fB--verbose\fP[=false]
	Enable verbose debug logging


.SH EXAMPLE
.EX
# Open an editor to write/edit the description
pogo describe

# Set description directly from command line
pogo describe -m "feat: add user authentication system"

# Use aliases for shorter commands
pogo desc -m "fix: resolve memory leak in data processor"
pogo rephrase -m "docs: update API documentation"
.EE


.SH SEE ALSO
\fBpogo(1)\fP