agentleFS
is-bois-bo/fullstack-forge-skill/.agents/skills/forge/SKILL.md

forge

Skill2 starsChanged 3 months agoApache-2.0View on GitHub

Use automatically for installed software engineering: build, change, fix, review, audit, test, verify, deploy, release, or ship. Apply production discipline proportionately; explicit commands are optional. Not for unrelated conversation.

78 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use forge-review, forge-design and 8 more.

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.
  • tonmoy007Skill

    forge-review

    Run a multi-dimensional parallel code review over the current change.

    Also in 8 projects that use this

  • DailenGSkill

    forge-design

    Design, UX, and polish discipline for the forge lifecycle. Covers the design tier, the design brief in docs/DESIGN.md, UX requirements and their verification methods, the per-slice design pass, the UX defect register, and the release polish pass. Load whenever work touches a user-facing surface (GUI, terminal, library API, or operated service), whenever a UX observation needs disposing of, and whenever a release is in reach.

    Also in 3 projects that use this

  • DshamirSkill

    forge-plan

    Takes analysis.json + budget cap → derives the full phase sequence, hyperparameters, instance type, cost estimate, and acceptance thresholds. Emits plan.md (the single human gate document) and plan.json (the machine-readable spec that dispatch-v2 consumes). Refuses to plan if estimated cost exceeds budget×1.2.

    Also in 4 projects that use this

  • tonmoy007Skill

    forge-build

    Run Stage 6 of the Forge pipeline — implementation. Use when the user says

    Also in 3 projects that use this

  • TT-WangSkill

    forge-status

    Show current forge project status, plan, and iteration history

    Also in 3 projects that use this

  • SupabaseSkill

    spark

    Spark REST API for database schema, data, and email/password authentication.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 67 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not edit this adapter; edit the canonical playbook instead.

    line 26

“Common” is measured: kept by at least 6 in 10 of the 67 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- fullstack-forge:managed-adapter v1 skill=forge canonical=../../../.fullstack-forge/skills/forge/SKILL.md -->

Fullstack Forge adapter: forge

This file is a pointer maintained by Fullstack Forge. It exists so this agent host can discover and trigger the skill. The full playbook is not duplicated here: one canonical copy is shared by every installed host.

Read the canonical playbook now and follow it exactly:

../../../.fullstack-forge/skills/forge/SKILL.md

That path is relative to this file. From the installation root it is .fullstack-forge/skills/forge/SKILL.md. Every resource the playbook references (fullstack-forge/references/..., fullstack-forge/schemas/..., fullstack-forge/templates/..., fullstack-forge/profiles/...) resolves relative to .fullstack-forge/skills/. The canonical playbook owns any deterministic composition step; perform that step exactly once. This adapter never adds a second workflow or composition command.

Do not edit this adapter; edit the canonical playbook instead. If the canonical file is missing or unreadable the installation is damaged. Report it and repair through the same project-package, archive, or plugin mechanism that installed this adapter. Never fall back to an unpinned npx forge, which may resolve an unrelated public package.

Download now (ZIP)

Does 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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.