skills.rest
manhthien2005
manhthien2005COMMUNITY
Explore all skills by this author →
WebsiteGitHub

detailed-feature-review

Evaluate feature source code against architecture standards, SRS, and JIRA with a 100-point score.

Updated Mar 3, 2026
Search Tags:#code review#clean architecture#scoring#jira#quality audit#feature evaluation#srs compliance
One-click install
npx skills add https://github.com/manhthien2005/PM_REVIEW --skill detailed-feature-review-manhthien2005
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: detailed-feature-review
Source: https://github.com/manhthien2005/PM_REVIEW/tree/main/tooling/.windsurf-template/shared/skills/detailed-feature-review
Command: npx skills add https://github.com/manhthien2005/PM_REVIEW --skill detailed-feature-review-manhthien2005

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Development teams lack a consistent, evidence-based way to verify that a finished feature actually matches its SRS requirements, JIRA acceptance criteria, and architecture standards before release. This Skill performs a structured deep audit of actual source code and produces a scored Vietnamese review report that stakeholders can act on. ## Core Features & Use Cases - 8-Criterion Scoring (100 points): Scores feature correctness, API design, architecture, validation, security, code quality, testing, and documentation using detailed rubrics in references/evaluation-criteria.md. - SRS & JIRA Cross-Verification: Compares UC main/alternative/exception flows and JIRA acceptance criteria against the real implementation, flagging discrepancies with severity levels. - Re-review Protocol: Detects previous review files, extracts old scores and weaknesses, and appends a comparison section showing fixed, persisting, and newly introduced issues. - Use Case: A PM asks to review the Login feature of the AUTH module before merging. The Skill loads the MASTER_INDEX, reads the module summary and architecture standards, inspects the source files, scores 72/100, and saves REVIEW_ADMIN/AUTH_LOGIN_review.md with prioritized action items. ## Quick Start Ask the AI to review the Login feature of the AUTH module in the Admin project and generate the detailed scored report.

Frequently Asked Questions about detailed-feature-review

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

FAQPage Schema
How do I run a detailed code review on a specific feature?▼

Specify the feature name, module, and project (Admin or Mobile), for example: review the Login feature of the AUTH module in Admin. The Skill loads context from MASTER_INDEX, inspects the source files, scores 8 criteria out of 100 points, and saves a Vietnamese report.

What criteria does a feature code review evaluate?▼

It scores 8 criteria totaling 100 points: feature correctness (15), API design (10), architecture and patterns (15), validation and error handling (12), security (12), code quality (12), testing (12), and documentation (12). Scores of 76-100 pass, 51-75 need fixes, and 0-50 fail.

How does the review verify SRS and JIRA compliance?▼

It compares each use case main flow, alternative flow, and exception flow against the actual implementation, marking each as matched or not. It also maps JIRA Epics and Stories to the module and checks every acceptance criterion, flagging gaps with severity levels.

Can I re-review a module after fixes are applied?▼

Yes. The Skill searches for the previous review file, extracts old scores and weaknesses, then appends a comparison section showing score changes per criterion, fixed weaknesses, persisting issues, and newly introduced problems. The old file is overwritten, not duplicated.

What happens if the module or source code is missing?▼

If the module is not in MASTER_INDEX, the Skill lists available modules and asks you to choose. If the source folder is empty, it marks the feature as not built with an N/A score. Missing summaries are noted in the report while the review continues from source scanning.

When should I not use detailed feature review?▼

Do not use it for quick PR or commit self-reviews, debugging, writing new code, or generating test cases. For fast 5-axis PR checks use a lightweight code review skill, and for project-level overviews use a holistic review skill instead.

Related Skills

Explore More Software Engineering Skills→
mayurpisemayurpise
39

jira-create

Create Epic, Stories, and Sub-tasks in Jira from a jira-export.md file via MCP-Jira.

Community
Advanced
ronniepinnellronniepinnell

sprint

Review backlog items and prioritize work for upcoming sprints.

Community
Intermediate
atelier-fashionatelier-fashion
159

reflect

Audit recent code changes for correctness, conventions, architecture, and testing.

Official
Advanced
OpenLAIROpenLAIR
1.0k

inno-paper-reviewer

Automate structured manuscript and grant reviews using checklist-based evaluation.

Official
Advanced