agentleFS
Sign inStart free
is-bois-bo/fullstack-forge-skill/.agents/skills/forge-code/SKILL.md

forge-code

Skill2 starsChanged 3 months agoApache-2.0View on GitHub

Find correctness, maintainability, type-safety, error-handling, and dead-code risks in changed and critical paths.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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 an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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-code canonical=../../../.fullstack-forge/skills/forge-code/SKILL.md -->

Fullstack Forge adapter: forge-code

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-code/SKILL.md

That path is relative to this file. From the installation root it is .fullstack-forge/skills/forge-code/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.

Check your setup, free