post-task-review

Reviews completed dev tasks for code quality issues and documentation gaps.

Updated Jul 3, 2026

Search Tags:#software engineering #quality assurance #code review #documentation #refactoring #task review

Ready to run

npx skills add https://github.com/Reidond/Banshee --skill post-task-review-reidond

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: post-task-review
Source: https://github.com/Reidond/Banshee/tree/main/.claude/skills/post-task-review
Command: npx skills add https://github.com/Reidond/Banshee --skill post-task-review-reidond

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents incomplete task delivery by providing a structured review process that catches code issues, convention violations, documentation gaps, and missed learnings after significant changes.

Core Features & Use Cases

Comprehensive Code Review: Reviews implementation quality, edge cases, project conventions, and potential regressions after major changes.
Documentation Impact Analysis: Evaluates affected documentation using project-specific mappings and updates stale or missing information.
Learnings Extraction: Captures reusable discoveries, updates project knowledge, and tracks improvements after completed work.

Quick Start

Use the post-task-review skill to review my completed feature implementation and identify code, documentation, and process improvements.

Frequently Asked Questions about post-task-review

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

FAQPage Schema

How do I run a code review after completing a feature implementation?▼

To run a post-task code review, evaluate implementation quality, check edge cases, verify project conventions, and identify potential regressions using a structured review checklist after completing your feature implementation.

What is a post-task review in software engineering?▼

A post-task review is a structured validation process that checks completed development tasks for code quality issues, convention violations, documentation gaps, and process improvements to prevent incomplete task delivery.

How do I analyze documentation impact after a code refactor?▼

Analyze documentation impact by evaluating affected documentation using project-specific mappings, identifying stale information, and updating missing details after completing your code refactor or bug fix.

Can I use a task review checklist for specification-driven engineering workflows?▼

Yes, the task review checklist applies to specification-driven engineering workflows, feature implementations, refactors, and bug fixes, requiring documentation impact analysis and learning extraction procedures for consistent validation.

What's the best way to extract learnings from completed development tasks?▼

The best way to extract learnings is to capture reusable discoveries, update project knowledge, and track process improvements as part of a structured post-task evaluation after completing significant code changes.

When should I not use a post-task review process?▼

You should skip post-task reviews for minor or trivial changes, as the process targets significant development work requiring structured validation, convention checking, and documentation impact analysis to be effective.