implement-feature-reviewing

Compare Node.js and Go code against planning documents to produce pass/fail review checklists.

Updated Feb 2, 2026
One-click install
npx skills add https://github.com/thewind121212/natashi --skill implement-feature-reviewing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-feature-reviewing
Source: https://github.com/thewind121212/natashi/tree/main/.claude/skills/topic-review
Command: npx skills add https://github.com/thewind121212/natashi --skill implement-feature-reviewing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps review a feature implementation by comparing actual code against planning documents, ensuring architecture compliance for a Node.js + Go Discord music bot, and producing a pass/fail checklist report.

Core Features & Use Cases

  • Read planning documents from docs/plans/adr-{YYYYMMDD}-{feature-name}/ including implementations.md, impacts.md, and diagrams.md.
  • Scan actual code changes in both Node.js (playground) and Go (internal) projects, then check against the planning baseline.
  • Validate architecture and task alignment, and generate a detailed review checklist with clear pass/fail status.

Quick Start

Run the feature-reviewing skill after implementing a feature to generate a comprehensive review checklist.

Frequently Asked Questions about implement-feature-reviewing

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

FAQPage Schema
How do I automate feature review for a Node.js and Go Discord bot?

This skill automates feature review by scanning Node.js and Go code changes, comparing them against planning baseline documents, and generating a pass/fail checklist report.

How does code review against planning documents work?

Code review against planning documents works by reading the implementation and impact files from the docs/plans directory, verifying actual code changes match the baseline, and outputting a structured review report.

What format should planning documents be in for feature review?

Planning documents must be placed in docs/plans/adr-{YYYYMMDD}-{feature-name}/ and include implementations.md, impacts.md, and diagrams.md to serve as the review baseline.

Can I validate architecture compliance for both Node.js and Go projects?

Yes, you can validate architecture compliance for both Node.js and Go projects by scanning actual code changes in both environments and checking them against the defined planning baselines.

What is the best way to generate a QA checklist for feature implementations?

The best way to generate a QA checklist is to run an automated feature review that validates task alignment and architecture compliance, producing a detailed pass/fail status report for the implementation.