skills.rest
bmsull560
bmsull560COMMUNITY
Explore all skills by this author →
GitHub

jr-architect-review

Validate architectural coherence across code, tests, and documentation before merge.

Updated Apr 8, 2026
Search Tags:#integration#diff#code-review#architecture-review#regression-testing#requirements-traceability
One-click install
npx skills add https://github.com/bmsull560/Fabric_4L --skill jr-architect-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jr-architect-review
Source: https://github.com/bmsull560/Fabric_4L/tree/main/.windsurf/skills/jr-architect-review
Command: npx skills add https://github.com/bmsull560/Fabric_4L --skill jr-architect-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies and validates architectural coherence in a completed feature to ensure integration integrity across components.

Core Features & Use Cases

  • Branch-diff driven review: compares feature changes against base to surface integration issues.
  • Cross-task coherence assessment: ensures design, API contracts, and implementation align across tasks.
  • Downstream readiness: checks for API stability, test coverage, and documentation implications for dependents.
  • Acceptance criteria mapping: verifies traceability between tickets, tasks, tests, and quality gates.
  • Regression awareness: identifies potential ripple effects and preparedness for broader testing.

Quick Start

Review the feature by inspecting the feature tickets and performing a full branch diff against the feature base.

Frequently Asked Questions about jr-architect-review

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

FAQPage Schema
How do I check architectural coherence before merging a feature branch?▼

Cross-task coherence assessment verifies that design, API contracts, and implementation align across all tasks within a completed feature, preventing integration gaps and ensuring traceability.

What is the best way to map acceptance criteria to tests and tickets during code review?▼

Downstream readiness assessment checks API stability, test coverage, and documentation implications to ensure dependents are prepared, while also identifying potential ripple effects for broader regression testing.

How do I assess downstream impact and regression risks in a pre-merge review?▼

For pre-merge feature review, you need completed feature tickets and a full branch diff against the feature base to accurately perform cross-task coherence checks and traceability validation.

Can I use branch-diff analysis to validate requirements traceability across components?▼

Other code-review approaches in the same category may focus on style or syntax, whereas branch-diff driven architectural review specifically targets cross-task coherence, downstream readiness, and integration integrity.

Related Skills

Explore More Software Engineering Skills→
leighmccullochleighmcculloch
1

github-issue-from-wip

Generates a draft GitHub issue from the current branch's uncommitted changes.

Community
Intermediate
dsivovdsivov

release-validation

Automate production-release readiness assessment for development branches.

Community
Advanced
EdanStarfireEdanStarfire
15

requirement-validator

Validate task requirements for clarity, completeness, specificity, testability, and feasibility.

Community
Basic
honysyanghonysyang
18

code-review

Automate Python code review with style checking and linting.

Community
Basic