Interactively author a new Studio skill, hook, or template file-package — describe the job, draft the package one turn at a time, iterate on operator feedback, and save it once the operator is satisfied.
parsoFish/forge-studio
SkillsMP has collected 35 skills from parsoFish/forge-studio. Open a skill to review its source and details.
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 35
- GitHub stars
- 3
- GitHub forks
- 0
Skills in this repository
Showing 35 of 35 collected skills.
Implement a plan and make the project's checks pass.
Turn a unit of work into a short, concrete implementation plan a dev agent can execute.
Review the implemented change against the plan and report what's right and what's not.
forge's plan agent — decomposes the architect's finalised initiative into atomic, dependency-ordered spec-work-items (ADR-015's versioned artifact contract) for the develop agent's ralph loop to consume.
forge's adversarial review agent — initiative-context critique of the developed diff, distinct from the demo's AC-proof: correctness, regression risk, contract-fit, convention drift (project-brain advisory). Emits a findings artifact with per-finding severity…
Adversarial completeness review of drafted initiative manifests against the session's idea, interview, and PLAN — before they promote to the queue.
Interactive ideation session that turns ideas into a PLAN.md the operator reviews before any manifest is queued.
Apply a single targeted fix to one brain theme file to clear a specific lint finding emitted by forge brain lint.
Append raw sources to the brain and create or update theme pages. Never modifies raw in place; never deletes.
The declaration carrier and display identity for the onboard-project flow's contract gate — the REAL forge↔project contract preflight (runPreflight, cli/preflight.ts) runs orchestrator-side (ADR-036); never spawned via the flow path (the only path…
forge's demo agent — takes a develop phase's output and composes the initiative's demo from the studio demo-element library and the project's typed demoProcess, authoring demo.json (with per-AC acEvaluations) against the initiative's acceptance criteria.…
Author a project's reusable demo-generation skill — the machinery that showcases an initiative's CHANGES (before/after) as a Forge-styled HTML page — and render a real sample from a recent change, iterating on operator feedback until locked.
Launch the Ralph loop runner for a single work item; iterate until quality gates pass, iteration budget is exhausted, or the loop is detected as wedged.
Interactively author a project's AGENTS.md (the single agent-instruction file) via a claude-init-style back-and-forth, confirmed by the operator before it is written.
Bring an existing project up to the forge↔project contract so forge can develop it unattended — declare the quality gate, converge preflight to contract-green, bind the KB, and report what remains.
Apply one operator-approved fix to a managed project to clear a specific forge preflight contract clause.
Read a managed project from scratch and author its initial brain — real theme pages (patterns, conventions, structure) grounded in the project's current state.
Audit a managed project's actual end state — code, tests, docs, release surface — against the roadmap/initiative intents that were supposed to produce it, hunting drift (promised-but-absent capabilities, orphaned/half-landed work, doc/code contradictions,…
Run a deep structured retrospective at the end of a merged initiative — repeated actions, roadblocks hit, and operator notes (agentic self-reflection + agent-prompted user questions + pure user feedback) — and write the findings into the central forge-owned…
After the operator approves a merged-ready cycle, finalise the release on the PR branch — compute the semver bump, promote the draft changelog entry to a versioned section, run the project's declared pre-merge release steps, optionally bump the version file,…
Interactively turn a set of agent-tier brain-lint findings for one KB into a reviewable cleanup plan — never edits a brain file itself.
Summarise a git diff into three bullet points — what changed, why it matters, and what to test.
Review a branch's dependency changes before merge — new direct and transitive packages, version jumps, and lockfile churn that the code diff alone does not show.
The canonical forge demo capability — how forge runs a demo, what every demo must contain, and how the demo maps to the forge UI review page. A demo makes ONE behavioural delta (prior → new) visible, grounded in the initiative's acceptance criteria. The demo…
Bring any code project up to the forge↔Studio project contract so forge can develop it unattended at roadmap scale. Use before pointing forge at a new or not-yet-primed managed project. Works for any form — UI app, HTTP API, library, CLI, monorepo, infra…
Forge-owned generator skill that reads a project's demoProcess + its actual code and generates per-project demo machinery (a repo skill and/or CI step and/or test) committed into the project repo. Run when an operator saves a project's demoProcess in Studio.…
Structural integrity checks on the brain — frontmatter, index sync, source links, staleness, orphans, length cap, contamination, contradictions. Thin invoker of `forge brain lint`.
Efficient lookup against the brain via markdown keyword scan. Logs gaps so the next ingest pass can fill them. Accepts a scope parameter to target the right brain: forge-dev, cycles, project, or all.
Compute the next semantic version and a finalised changelog entry from a cycle's acceptance-criteria categories. Reads the draft Unreleased changelog section (or the cycle's AC list), maps categories to a semver bump (breaking-change marker → major; new…
Rule-based, directory-by-directory cleanup of generated/abandoned/scratch cruft from the forge tree. Every removal is justified by an EXPLICIT rule, never a hardcoded path, so the rule set stays auditable and adjustable. Reports a plan before deleting;…
Detect the documentation surface a change touched and refresh it using the project's own declared doc tool, then stage the result. Maps the diff to the docs that describe it (generated reference docs via the project's generator command, hand-written…
Compress the current session into a markdown transfer document — open threads, decisions made, and context consumed — so another agent or a human can resume without re-deriving state.
Interview the developer on a work-item spec BEFORE writing any code — surface gaps, false assumptions, and scope creep while they are still cheap to fix.
Keep the UI-journey demo harness (scripts/journeys/) in sync with forge-ui changes. Use whenever a change touches forge-ui load-bearing state (data-* attributes, routes, surfaces, flows/agents/skills/KB affordances), when adding or retiring a Studio…