Generate code and analyze complex systems with a single prompt.
npx skills add https://github.com/geekjourneyx/agora --skill forge-geekjourneyx
Please help me install this Agent Skill. Skill: forge Source: https://github.com/geekjourneyx/agora/tree/main/rooms/forge Command: npx skills add https://github.com/geekjourneyx/agora --skill forge-geekjourneyx
The Forge skill helps you resolve engineering and architecture decisions by gathering code evidence and producing a structured, adversarial recommendation instead of settling on intuition.
Use case: You are deciding between monorepo vs polyrepo for a system with active development, and you want a decision grounded in the current repository structure, change history, and practical maintainability risks.
Ask Forge: "Use /forge --triad architecture 'Should we use monorepo or polyrepo?' and provide an evidence-based verdict with risks and next steps."
High-intent search queries and answers about installing and using this skill.
To make an architecture decision based on code evidence, you need structured deliberation that gathers repository data, inspects git history, and runs tests before delivering a verdict. This approach forces evidence-backed analysis for engineering trade-offs.
Evaluating monorepo vs polyrepo trade-offs requires analyzing current repository structure, change history, and maintainability risks. An adversarial panel approach synthesizes these opposing architectural options into a single, justified recommendation.
Structuring a code review for refactoring decisions involves mapping file structures and searching code patterns to gather evidence. A dialectical synthesis process integrates opposing viewpoints into a clear implementation path with rationale.
Yes, you can get a quick architecture recommendation when time is limited by using a reduced deliberation mode. Quick or Duo modes match varying time constraints while still gathering repository evidence to produce a synthesized verdict.
Debugging complex multi-repo systems benefits from adversarial analysis because it forces evidence gathering like dependency checks and git history inspection before deciding. This prevents premature fixes by validating hypotheses against actual repository state.
Andreicr1Trace code evolution via git log, blame, and shortlog.
HerbertJulioReview changed files for architecture, types, security, and test coverage.
Himanshu040604Audit GitHub repository URLs for malicious code and supply chain risks.
ohta-rhAnalyze engineering topics with parallel MAGI agents and synthesize structured judgments.
