fcc-7-audit-patch

Audits six-chapter thesis drafts with three parallel reviewers and applies structured patches.

93|Updated Jul 19, 2026
One-click install
npx skills add https://github.com/1542740346-png/fcc-compiler-v5.1 --skill fcc-7-audit-patch-1542740346-png
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fcc-7-audit-patch
Source: https://github.com/1542740346-png/fcc-compiler-v5.1/tree/main/fcc-7-audit-patch
Command: npx skills add https://github.com/1542740346-png/fcc-compiler-v5.1 --skill fcc-7-audit-patch-1542740346-png

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Final-stage thesis review for Chinese accounting case-study papers is slow and inconsistent when done by a single pass. This Skill runs the Phase 7 terminal audit: mechanical rule scanning, three independent parallel reviewers, structural validation, collapse testing, and severity-tiered patch application with loop-back routing to earlier phases. ## Core Features & Use Cases - Three Parallel Reviewers: Spawns independent sub-agents for argument-chain integrity, rule compliance (25 writing rules), and Red Thread cross-chapter consistency, each producing unified findings JSON. - Mechanical Scanning & Structural Validation: Runs chapter_check.py for symbol/parenthesis violations, verifies chapter word counts, reference counts, and performs a collapse stress test on conclusions. - Patch Block & Loop Rule: Applies severity-tiered fixes (critical/major/minor) with a patch log, and routes root-cause findings back to earlier phases (Phase 1-5) instead of patching symptoms. - Use Case: After completing all six thesis chapters, run this Skill to get a merged findings report, applied patch log, and loop-back recommendations before generating the final Word document. ## Quick Start Run the Phase 7 final audit on my six chapter drafts in output/ and produce the merged findings report, patch log, and loop-rule routing suggestions.

Frequently Asked Questions about fcc-7-audit-patch

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

FAQPage Schema
How do I run a final audit on a multi-chapter thesis draft?▼

Run the Phase 7 audit after all six chapters are complete. It executes mechanical scanning with chapter_check.py, then launches three parallel reviewers covering argument chains, rule compliance, and Red Thread consistency, and finally applies severity-tiered patches.

What do the three parallel reviewers check in a thesis?▼

Reviewer A checks argument-chain integrity such as evidence support and theory usage. Reviewer B checks surface rule compliance like parentheses, paragraph first sentences, and citation zones. Reviewer C checks Red Thread consistency across chapters, including promise fulfillment and Ch4-Ch5 alignment.

Can this Skill run before all six chapters are finished?▼

No. The init protocol reads project_state.md and stops with a warning if Phase 6 is not marked COMPLETED. All six chapter drafts in output/ must exist before the audit begins.

What happens to findings that cannot be fixed by text patches?▼

Findings rooted in earlier phases are handled by the Loop Rule instead of direct patching. The orchestrator outputs a routing report sending issues like insufficient evidence back to Phase 4 or unused theories back to Phase 3 for structural fixes.

What output files does the Phase 7 audit produce?▼

It writes four artifacts to the research/ folder: phase7-merged-findings.json, phase7-patch-log.json, phase7-loop-rule-report.md, and phase7-structural-validation.md. It also updates the Phase 7 status section in project_state.md.