ai/gemini-content-team/skills/project-identity/SKILL.md
Derive ai-brain project name and KB path from git remote or folder name — same algorithm as Cursor kb-identity (worktree-safe). Use before resolving content-brain paths.
npx skillsauth add akshay-na/dotfiles project-identityInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Parity: Same resolution as Cursor ~/.gemini/skills/kb-identity/SKILL.md (after DotMate stow) → durable path ~/ai-brain/projects/<project_name>/. Keep algorithm aligned if you edit either skill.
project_root: absolute path to the working copy (git repo root, worktree checkout, or non-git folder).project_name: lowercase slug (from origin URL last segment or directory basename).content_brain / kb_path: ~/ai-brain/projects/<project_name>/ with ~ expanded to $HOME.project_root/.git is a directory → read project_root/.git/config.project_root/.git is a file (worktree) → parse gitdir: line → find main repo’s .git/config (path up to and including .git before /worktrees/) and read that config.remote_url[remote "origin"] → url = ...derived_from = folder_nameproject_nameremote_url set → last path segment of repo path, strip .git, lowercase (HTTPS, git@host:, ssh:// — same rules as kb-identity).basename(project_root).toLowerCase()content_brain = $HOME/ai-brain/projects/<project_name>/
Use project_name only (not full_identity hash) for the directory name — matches kb-identity Step 5 / kb_path.
.git at project_root: still allow project_name = basename(project_root) for non-git folders (optional: treat as not_git_repo if policy forbids — default allow folder fallback).Handled in rules/brain-paths.md / rules/project-identity.md:
GEMINI_CONTENT_BRAIN — absolute path bypasses derivation.GEMINI_PROJECT_ROOT — forces project_root for derivation.Agents may cache (project_root → content_brain) for the invocation; invalidate if project_root or origin changes.
development
Discovery + naming convention reference for typed dev/SME/QA/devops team members in any workspace folder. Primary consumer: `tech-lead` (org-tier).
devops
Automated task classification, agent selection, and state tracking. Use when routing tasks to agents, selecting pipelines, or managing task state.
testing
Use when designing scalable systems, evaluating consistency models, planning state management, making architectural decisions, or when trade-offs around coupling, failure isolation, and reversibility need explicit reasoning before implementation.
tools
CTO/tech-lead helper — split work into disjoint shard briefs with caps (instance_cap, partition_basis, determinism keys).