skills.rest
farzanmrz
farzanmrzCOMMUNITY
Explore all skills by this author →
GitHub

feature-qc

Run a full quality-control battery on a feature branch.

Updated Jul 18, 2026
Search Tags:#code review#quality control#feature branch#documentation sync#build verification#boot smoke
One-click install
npx skills add https://github.com/farzanmrz/beat-radar-agent --skill feature-qc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-qc
Source: https://github.com/farzanmrz/beat-radar-agent/tree/main/.claude/skills/feature-qc
Command: npx skills add https://github.com/farzanmrz/beat-radar-agent --skill feature-qc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill runs the full quality-control battery for a feature branch so you can catch review issues, build failures, boot regressions, and stale documentation before merge.

Core Features & Use Cases

  • Branch convergence checks: Verifies the branch is cleanly consolidated with no stray worktrees or branches.
  • Multi-angle review and fix pass: Runs a coordinated QC review, applies valid findings, and delta-verifies the fix diff to avoid introducing new defects.
  • Build, boot, and doc validation: Formats and lints the changed files, confirms the app builds and starts successfully, and syncs documentation only when a change is truly non-recoverable.
  • Use case: A developer finishes a feature slice and wants an end-to-end confidence pass that the branch is safe to ship or hand off.

Quick Start

Run the feature-qc skill to validate the current feature branch end to end and report any findings or remaining risks.

Frequently Asked Questions about feature-qc

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

FAQPage Schema
How do I run quality control checks on a feature branch before merge?▼

Feature branch quality control involves running a full validation battery that checks branch convergence, reviews diffs, applies fixes, and verifies build and boot health to ensure the branch is ready for merge or handoff.

What does branch convergence verification check for in feature work?▼

Branch convergence verification checks that a feature branch is cleanly consolidated with no stray worktrees or branches, ensuring all in-progress feature work is properly unified before proceeding to build and boot health validation.

Do I need GitHub CLI and pnpm installed to validate my feature branch?▼

Yes, validating a feature branch end-to-end requires git, GitHub CLI, pnpm, and the repository's QC workflow and helper scripts. These dependencies coordinate the review, linting, startup, and documentation sync processes.

How does documentation sync detect stale docs during feature branch review?▼

Documentation sync during feature branch review identifies non-recoverable documentation drift caused by code changes. It syncs documentation only when a change is truly non-recoverable, preventing stale docs from persisting through merge.

What is the best way to catch boot regressions before handing off a feature branch?▼

The best way to catch boot regressions is running an end-to-end confidence pass that formats and lints changed files, confirms the app builds and starts successfully, and delta-verifies any applied review fixes to avoid introducing new defects.

Related Skills

Explore More Software Engineering Skills→
auerbachbauerbachb
3

merge

Squash-merges pull requests and deletes branches after verifying CI and acceptance criteria.

Community
Advanced
hutchichutchic
8

ensure-feature-branch

Create and checkout a feature or bug branch when on a mainline or release branch.

Community
Intermediate
nanorepublicananorepublica
61

Global Tech Stack

Validate code against centralized global tech stack standards.

Community
Basic
csim-sgcsim-sg

using-git-worktrees

Create isolated Git worktrees for feature branches with safety checks.

Community
Intermediate