/clientissues

Browse open client issues ready for development, pick one, and complete the full development cycle in one flow.

Usage 

/clientissues

Parameters

None.

What It Does

This is the all-in-one command that orchestrates the entire development workflow:

1. Fetch Open Issues (Cascading Priority)

Queries the client project (vinum/vinum) for open issues labeled Stage::Ready for Dev, in priority order:

Tier Criteria Description
1 quick-fix label Quick fixes — handled first
2 Priority::P0 or Priority::P1 High priority issues
3 All Stage::Ready for Dev Everything else

Stops at the first tier that returns results.

2. Select an Issue

Displays the matching issues with a short summary each. You pick which one to work on.

3. Full Workflow

Executes these commands in sequence:

  1. /clientissue — analyze, create dev issue, implement
  2. /techdebt — scan for technical debt in touched files
  3. /learnings — capture session knowledge
  4. /rollout — commit and push with issue reference
  5. /merge — create and merge MR (you choose staging or main)
  6. /clientfeedback — post German status update with time tracking

Authentication

This command uses the team API key (GITLAB_API_KEY_TEAM from .env) for all client-project interactions. Development project commands use the default glab authentication.

Prerequisites

  • glab must be authenticated
  • Working tree must be clean
  • .env file must exist in the project root with GITLAB_API_KEY_TEAM or GITLAB_API_KEY