Run any Skill in Manus with one click

architecture-consolidation

Stars18

Forks8

UpdatedJuly 16, 2026 at 13:46

Analyzes the whole codebase, asserts whether it is aligned with the high level guidelines, identifies transgressions, proposes fixes.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

ecmwf

ecmwf/forecast-in-a-box

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	architecture-consolidation
description	Analyzes the whole codebase, asserts whether it is aligned with the high level guidelines, identifies transgressions, proposes fixes.

Act as a critically-thinking software architect.

Read thoroughly the guidelines at backend/development.md
Check the list of known breaches and non-breaches at docs/developer/changeSpecs/overallReviewState.md.
Inspect the codebase in backend/src/* and backend/packages/*/src for where it is conflicting with the guidelines. Do not make changes to the codebase itself, only find where there is misalignment. You can spawn subagents for individual submodules and parts of the guide.
Write the results to the file docs/developer/changeSpecs/overallReviewResult.md. Format it into sections, such that each section can be taken by a software developer / agent, as a task for fixing. Refer to which element from the guideline the section addresses, and which files and their parts constitute the breach, and possibly hints or options for fixing. Do not list there items which have already been flagged as ignorable by being included in the overallReviewState.md.
If you identify anything which you think should be added to overallReviewState.md, to make future reviews easier, do so. And, on the other hand, if you think something from the overallReviewState.md has become obsolete and should be removed from there, do so as well.
Commit the changes, do not push.

More from this repository

same repository

fiab-meeting

ecmwf/forecast-in-a-box

Triage a Forecast-in-a-Box team meeting transcript against the GitHub board — propose new high-level issues, status changes, and PR links, then apply them only after the user approves the full plan.

2026-07-2218

release-helper

ecmwf/forecast-in-a-box

Analyze the changes compared to latest releases. Helps determine which releases should be triggered, and provides release notes for them.

2026-07-1718

adapt-pr-comments

ecmwf/forecast-in-a-box

Fetches unresolved comments from the specified PR and applies the fixes.

2026-07-1018

frontend-impact

ecmwf/forecast-in-a-box

Analyzes the changes made in the current branch to the codebase in `backend/`, determines how those changes impact the `frontend/` codebase, and writes minimalistic fixes to resolve compatibility issues.

2026-07-1018

name	architecture-consolidation
description	Analyzes the whole codebase, asserts whether it is aligned with the high level guidelines, identifies transgressions, proposes fixes.

Act as a critically-thinking software architect.

Read thoroughly the guidelines at backend/development.md
Check the list of known breaches and non-breaches at docs/developer/changeSpecs/overallReviewState.md.
Inspect the codebase in backend/src/* and backend/packages/*/src for where it is conflicting with the guidelines. Do not make changes to the codebase itself, only find where there is misalignment. You can spawn subagents for individual submodules and parts of the guide.
Write the results to the file docs/developer/changeSpecs/overallReviewResult.md. Format it into sections, such that each section can be taken by a software developer / agent, as a task for fixing. Refer to which element from the guideline the section addresses, and which files and their parts constitute the breach, and possibly hints or options for fixing. Do not list there items which have already been flagged as ignorable by being included in the overallReviewState.md.
If you identify anything which you think should be added to overallReviewState.md, to make future reviews easier, do so. And, on the other hand, if you think something from the overallReviewState.md has become obsolete and should be removed from there, do so as well.
Commit the changes, do not push.