completing-a-task

Complete routed software tasks by committing, pushing, creating PRs, commenting on tickets, and notifying reviewers.

18|9|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/arozumenko/sdlc-skills --skill completing-a-task
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: completing-a-task
Source: https://github.com/arozumenko/sdlc-skills/tree/main/skills/completing-a-task
Command: npx skills add https://github.com/arozumenko/sdlc-skills --skill completing-a-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents tasks from being considered complete when code exists but the required handoff steps—commit, push, PR, ticket comment, and reviewer notification—have not all happened in order.

Core Features & Use Cases

  • Five-step completion protocol: Ensures the task is truly done by completing an ordered sequence of delivery and communication actions.
  • Platform-aware execution: Translates host and tracker operations (Git host + issue tracker/boards) so the steps map correctly to GitHub, GitLab, Bitbucket, Azure DevOps, and other supported systems.
  • Verification and blocker handling: Requires local verification (tests and checks) before committing/publishing, and forces explicit reporting when any step is blocked.
  • Use Case: When you complete a routed feature, this skill guides you through turning implementation into a review-ready, traceable change with the proper ticket audit trail.

Quick Start

Ask the AI to complete your routed task by running verification, creating a feature branch, pushing it, opening a PR tied to the issue, commenting on the ticket, and notifying the reviewer as the final step.

Frequently Asked Questions about completing-a-task

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ensure my code changes are truly done before a PR handoff?

A proper PR handoff requires a five-step completion protocol: local verification, commit, push, PR creation, ticket commenting, and reviewer notification, ensuring both code delivery and an audit trail.

What steps are needed to create a review-ready PR with a ticket audit trail?

Creating a review-ready PR with an audit trail requires running local checks, committing code, pushing a feature branch, opening a PR tied to the issue, commenting on the ticket, and notifying the reviewer.

Does this task completion workflow support GitLab and Azure DevOps issue trackers?

Yes, the task completion workflow is platform-aware, translating host and tracker operations to map correctly to GitHub, GitLab, Bitbucket, Azure DevOps, and other supported Git hosts and issue trackers.

What happens if local verification or push fails during the PR workflow?

If any step in the PR workflow fails, the protocol forces explicit structured blocker reporting, preventing the task from being considered complete until the issue is resolved and all steps finish in order.

Why do I need to comment on an issue ticket after opening a pull request?

Commenting on the issue ticket after opening a pull request is required to establish a traceable audit trail, linking the code delivery to the original issue and ensuring the definition of task completion is met.

Can I use GitHub gh commands to automate reviewer notification and ticket updates?

Yes, you can use GitHub gh commands to automate the final handoff steps, pushing the feature branch, opening the PR tied to the issue, commenting on the ticket, and notifying the reviewer to complete the audit trail.