From my-serena
Activates an already-registered Serena project for the current session. Triggers on 'No active project' errors, 'activate Serena', 'start Serena session', 'make Serena work', or when Serena tools are not responding at session start despite the project being already registered.
npx claudepluginhub bartekck/bartek-marketplace --plugin my-serenaThis skill uses the workspace's default tool permissions.
Activate an already-registered Serena project for the current session so that semantic coding tools become available.
Provides IDE-like semantic symbol operations for large codebases: find/rename/refactor symbols, cross-file reference tracking, project memory, multi-language navigation.
Guides use of Serena's LSP tools for symbol overviews, finding definitions, tracing references, and codebase exploration where grep is imprecise.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
Activate an already-registered Serena project for the current session so that semantic coding tools become available.
This skill applies when:
.serena/project.yml configuration file (already registered)get_current_config returns "No active project" errorIf .serena/project.yml does not exist, the project is not yet registered. Use the serena-project-init skill instead to perform full registration.
Serena separates registration from activation by design:
serena project create) is persistent — it writes .serena/project.yml to disk and only needs to happen once.activate_project MCP tool) is an in-memory operation — it must happen each time a new session starts with the Serena MCP server.This means every new conversation or session requires calling activate_project before any other Serena tools will work.
Determine the project name or path. Options:
.serena/project.yml (the project_name field)get_current_config — it lists known projects by name in its error messageCall the activate_project MCP tool:
activate_project(project="<project-name-or-path>")
Either the registered project name or the absolute directory path works. On success, all Serena semantic tools become available.
Call get_current_config to confirm the project is now active. A successful response returning configuration data (rather than a "No active project" error) confirms activation succeeded.
Call check_onboarding_performed to determine whether onboarding data exists for this project. If onboarding has not been performed, consider running onboarding() to let Serena analyze the project structure, build systems, and testing frameworks.
The project name may not match what was registered. Try:
.serena/project.yml for the exact project_name valueget_current_config to see the list of known projectsCheck that the configured language servers can start:
.serena/project.ymlpyright for Python, typescript-language-server for TypeScript)Only one project can be active at a time. Activating a new project deactivates the previous one. To switch projects, call activate_project with the new project name or path.
If the .serena/project.yml is corrupted or misconfigured, delete it and use the serena-project-init skill to register the project again from scratch.
serena-project-init skillserena-project-init skill