agentleFS
Sign inStart free
lucastosettolucastosetto/dev-skills/skills/project-profile/SKILL.md

project-profile

Skill0 starsChanged 25 days agoMITView on GitHub

Load, discover or update the current project's dev-skills profile: issue tracker, PR host, base branch, CI, test/lint/boot commands, staging and production deploy, feature flags, observability, analytics, console access, API docs and project-specific skills, plus the user's own notes. Every dev-skills skill runs this first. Also use when the user says "remember for this project: ...", "show project profile", "refresh profile", or a profile fact turns out to be wrong.

  • Reads credentials

6 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use tdd.

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

    tdd

    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Follow ../../shared/policy.md (relative to this skill's folder).

    line 13
  2. Very specific:

    Exists: read it. Done, unless the caller needs a field that is unknown: discover just that field (step 3) and update the file.

    line 21
  3. Very specific:

    Do not ask the user to confirm anything: inferred facts are marked inferred.

    line 24
  4. Very specific:

    Leave a field unknown rather than guessing without a signal.

    line 48
  5. Distinctive:

    When a skill's command from the profile fails (wrong test command, missing tool), rediscover that field, update it, and mention the change …

    line 77

“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

Follow ../../shared/policy.md (relative to this skill's folder).

1. Locate

Compute <project-slug> (see policy "Paths") for the repo at the current working directory, or the repo the task is about. The profile is ~/.dev-skills/profiles/<project-slug>.md. Worktrees of the same repo share the slug, so they share the profile.

2. Load or discover

  • Exists: read it. Done, unless the caller needs a field that is unknown: discover just that field (step 3) and update the file.
  • Missing: discover everything (step 3), write the file (step 4), and print a 5-10 line summary. Do not ask the user to confirm anything: inferred facts are marked inferred.

3. Discover

Reads only. Record each value with its source (file:line, command, or user) and confidence (confirmed when read directly from config or code, inferred when guessed from signals).

FieldSignals
pr_hostgit remote get-url origin host; tool available (gh, glab, Bitbucket MCP via ToolSearch)
tracker, ticket_keyticket keys in git branch -a and recent git log subjects; .github/ISSUE_TEMPLATE; links in README/CONTRIBUTING; connected tracker MCPs (ToolSearch "jira", "linear", "clickup"); app.clickup.com links
base_branch, branch_naming, pr_templategit symbolic-ref refs/remotes/origin/HEAD; recent branch names; .github/pull_request_template.md or similar; docs
ci.github/workflows, bitbucket-pipelines.yml, .gitlab-ci.yml, .circleci
commands.test, commands.lint, commands.boot, commands.setuprepo CLAUDE.md, README, CONTRIBUTING, docs/, package.json scripts, Makefile, Procfile, compose files, pre-commit config
env_files.env.example/.env.sample and which untracked env files the docs say to create
deploy.staging, deploy.prod, deploy.ordersee ../../shared/references/deploy.md "Finding the method"; docs; deploy scripts
flagsdependency files (see deploy.md "Feature flags")
errors, logs, metrics, traces, apmdependencies (sentry, rollbar, honeybadger, bugsnag, ddtrace, newrelic, opentelemetry, prometheus client); connected MCPs (ToolSearch "grafana", "sentry", "datadog"), mapped per environment
analyticsamplitude, mixpanel, segment, posthog, statsig, growthbook dependencies
consoleGemfile → Rails, manage.py → Django, ORM REPL; how prod console is reached if documented
api_docsopenapi.*, swagger.*, Postman collections (*.postman_collection.json), docs/api, API sections in README
docs_tool, chat_toolconnected Notion/Confluence/Google Drive, Slack MCPs
project_skills.claude/skills/*/SKILL.md and .claude/commands/*.md in the repo: name + one-line purpose, and which dev-skills step each replaces (e.g. a staging deploy skill → deploy staging)
related_repossibling repos with profiles that share the same tracker board; frontend/backend pairs under one parent folder

Leave a field unknown rather than guessing without a signal.

4. File format

# <project-slug>
Repo: <absolute path of main checkout> · Updated: <YYYY-MM-DD>

## Discovered
<!-- Rewritten by project-profile. Edit ## Mine instead. -->
- pr_host: github (gh) — git remote · confirmed
- tracker: jira, key DEV-\d+ — branch names · inferred
- commands.test: bin/rails test — README.md:42 · confirmed
- deploy.staging: project skill deploy-to-staging — .claude/skills · confirmed
- metrics: grafana-prod (prod), grafana-dev (staging) — connected MCPs · inferred
- analytics: unknown

## Mine
<!-- Yours. Never rewritten. A key here overrides the same key above. -->
### general
### implement
### deploy
### standup
### plan

Rewrite only ## Discovered. Never change ## Mine except to append a note the user asked to remember (policy "Project config") or a mode: line set by /dev-skills:mode ... project.

5. Keep it right

When a skill's command from the profile fails (wrong test command, missing tool), rediscover that field, update it, and mention the change in one line.

Output

For the caller: the facts it needs. For the user: the summary only when the profile was created or changed. When the user asked to see it, print the file.

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