forge-review
Skill0 starsChanged 2 months agoMITView on GitHub
Review a built source integration against its plan and the expert rules. Produces a PASS/FAIL report with findings by severity.
12 other projects use a version of this.
Adopted by
Most recently taken up by
- 3orionkings/forgetheir own version, first seen Nov 16, 2026
- brightstack/forgetheir own version, first seen Nov 8, 2026
- antonailog/forge-skillstheir own version, first seen Oct 25, 2026
- fabioalencar/forgedesigntheir own version, first seen Oct 20, 2026
- peterzat/OrgSmiththeir own version, first seen Oct 13, 2026
- yike-gunshi/forge-skillstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use forge-ship and Forge.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
redteamlifeSkillforge-ship
Use when the user asks to merge, release, promote, reconcile, or close out work in a repo containing `docs/forge/` or governed by FORGE. Not for per-task commits; those complete inside forge-execute-task.
Also in 5 projects that use this
ikennaokpalaSkillForge
Autonomous quality engineering swarm that forges production-ready code through continuous behavioral verification, exhaustive E2E testing, and self-healing fix loops. Combines DDD+ADR+TDD methodology with BDD/Gherkin specifications, 7 quality gates, defect prediction, chaos testing, and cross-context dependency awareness. Architecture-agnostic - works with monoliths, microservices, modular monoliths, and any bounded-context topology.
Also in 8 projects that use this
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- antonailog/forge-skills★ 15same name
- yike-gunshi/forge-skills★ 15same name
- brightstack/forge★ 13same name
- peterzat/OrgSmith★ 6same name
- tonmoy007/forge-plugins★ 2same name
- BrandedTamarasu-glitch/ForgeFlow★ 1same name
- fabioalencar/forgedesign★ 1same name
- khaledayeva/star-forge★ 1same name
- redteamlife/forge★ 1same name
- tinyorbit-ai/skills★ 1same name
2 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- forge-buildSkill
- forge-planSkill
- forge-testSkill
- sharedSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Read every file under sources/<source-name>/.
- Very specific: line 19
Read .claude/commands/experts/databricks.md sections on MERGE, watermarks, timestamps, numerics, clustering — the review is against them, …
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Forge Review
You are a senior data architect reviewing an integration for correctness, completeness and conformance. Findings are specific (file, line, what, why) — not a restatement of the checklist.
Input
/forge-review <source-name>
Steps
- Read
specs/<source-name>-integration-plan.md. - Read every file under
sources/<source-name>/. - Read
.claude/commands/experts/databricks.mdsections on MERGE, watermarks, timestamps, numerics, clustering — the review is against them, not against memory. - Validate against the checklist below. Grep for leftovers from the example source (
erp,sales_order) andTODO.
Review checklist
Plan fidelity
- Every planned bronze, silver and gold object has its config entry and notebook
- Column names, types and grains match the plan; deviations are listed in the plan's §12 or flagged
- Every gold column has a reason in the plan; no audit/operational columns leaked into gold
Conformance
- No new dimension duplicates a registry entry
- FK resolution mode matches the plan (
hashonly where the id namespace is shared) source_system_idis the registered one and appears on every gold row
MERGE and keys
- Merge keys equal the plan's declared grain; the source business key is among them
WHEN MATCHEDis gated withIS DISTINCT FROM(orbuild_merge_sqlis used)- Nullable merge keys use
<=> - Multi-version CDF input is deduplicated to one row per key before the MERGE
- No
F.lit(None)without a cast; notry: merge except: overwrite
Types and time
- Timestamps are UTC
*_at; noTIMESTAMP WITH TIME ZONE; DATE where a date suffices - Decimals are sized (
DECIMAL(p,s)); no bareDECIMAL; floats sized to the magnitude they can reach - Ratios stored 0–1; durations carry a unit suffix
Incremental correctness
- Watermark column is a bare indexed source column; lookback is set for mutable sources
- A second run over unchanged input writes 0 rows (the idempotency test is in the test plan)
Layout and performance
cluster_by≤ 4 columns, most-filtered first, time-first for event streams- No correlated scalar subquery in a projection; no CTE referenced more than once on the hot path
Security
- No credential values anywhere; only secret-scope key names
- PII columns identified in the plan and handled (mask, tag, or explicitly cleared)
Deployment
deploy.py --dry-runproduces the planned task graph- Tests cover every gold table: row count, unique grain, RI, FK resolution rate
Output
# <Source> Integration Review
## Verdict: PASS | FAIL
## Findings
### Critical (must fix) — file:line — what — why (link the expert section)
### Warnings (should fix)
### Info
## Files reviewed
## RecommendationDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

