agentleFS
Sign inStart free
juanitourquizajuanitourquiza/shipframe/skills/project-profile/SKILL.md

project-profile

Skill4 starsChanged 21 days agoMITView on GitHub

Read project-specific workflow rules before releases, deploys, onboarding, or custom repository conventions.

6 other projects use 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. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If no profile exists, state that ShipFrame will use the generic workflow and recommend creating .shipframe/profile.md for repeatable …

    line 43

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

Project Profile

Load project-specific rules that customize the generic ShipFrame workflow.

Lookup order

  1. shipframe.profile.md
  2. .shipframe/profile.md
  3. .shipframe/project-profile.md
  4. AGENTS.md sections mentioning ShipFrame, release, deploy, PR, tickets, or project rules
  5. WIKI.md and wiki/sync-config.md for documented repo boundaries

What to extract

  • Repo topology: root app, nested apps, multi-repo dependencies, generated artifacts.
  • Branching and release rules: base branch, protected branches, tags, release notes.
  • Verification rules: build, lint, tests, smoke URLs, screenshots, API checks.
  • Product rules: i18n, approved copy, client constraints, analytics, access control.
  • Deployment evidence: what must be shown before saying work is done.

Output

Return a concise profile summary:

## Project Profile Loaded

**Source files:** <paths read>
**Repo topology:** <summary>
**Release rules:** <summary>
**Verification rules:** <summary>
**Project-specific constraints:** <summary>
**Missing/unclear:** <items or "None">

If no profile exists, state that ShipFrame will use the generic workflow and recommend creating .shipframe/profile.md for repeatable project rules.

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