Review the SCBE-AETHERMOORE codebase for defects and governance risks.
npx skills add https://github.com/issdandavis/SCBE-AETHERMOORE --skill scbe-copilot
Please help me install this Agent Skill. Skill: scbe-copilot Source: https://github.com/issdandavis/SCBE-AETHERMOORE/tree/main/.claude/skills/scbe-copilot Command: npx skills add https://github.com/issdandavis/SCBE-AETHERMOORE --skill scbe-copilot
It provides full-system codebase reviews, enabling governance-aware code analysis, CI remediation, and cross-file repair guidance across the entire SCBE-AETHERMOORE stack.
Ask scbe-copilot to perform a full-codebase review for a pull request, identify CI failures, trace the root cause across files, and propose governance-aware fixes.
High-intent search queries and answers about installing and using this skill.
Governance-aware code review across multiple files requires full-codebase analysis to trace code flows, imports, and dependencies between modules. This process identifies defects and governance risks by maintaining cross-file context awareness, ensuring proposed changes adhere to project safety constraints.
Tracing CI failures to their root cause requires cross-file impact analysis to follow data flows spanning multiple directories. By understanding these module dependencies, you can identify the exact source file and propose targeted cross-file repairs to restore green builds.
Cross-file context analysis is the process of tracking relationships and data flows that span multiple directories to understand the full impact of a code change. You need it for bug tracing when a failure in one module originates from a dependency or import in another file.
Cross-file impact analysis can guide pull request reviews and merge decisions by surfacing root causes and evaluating dependencies across the entire codebase. This full-context review ensures that proposed changes maintain governance constraints and safety requirements before merging.
The best way to fix CI failures while maintaining governance constraints is to perform a full-codebase review that traces the failure source across files and proposes governance-aware fixes. This approach ensures cross-file repairs align with project safety rules before merging.
Full-codebase review is not ideal for isolated, single-file syntax fixes where cross-file context and dependency tracing are unnecessary. For changes with no impact on other modules, a full-system governance analysis adds overhead without providing actionable root cause insights.
bluejayACreate an isolated git worktree before code generation begins.
warpdotdevDiagnose CI failures for a pull request and generate a fix plan.
NoobyGainsEnforce code quality standards across pre-commit, pre-merge, and CI pipeline stages.
icartshAnalyze .NET solutions for code quality, security, and dependency issues.
