Discover Claude/Codex/Cursor session files for the current Salesforce repo and extract metadata. Internal helper for sf-sessions; not usually invoked directly. Trigger phrase: 'list sessions for this repo'.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sf-compound-engineering:sf-session-inventory [optional: repo path, defaults to current][optional: repo path, defaults to current]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Build an inventory of session files (timestamps, branches, sizes) scoped to the current Salesforce repo.
Build an inventory of session files (timestamps, branches, sizes) scoped to the current Salesforce repo.
<feature_description> #$ARGUMENTS </feature_description>
sfdx-project.json presence or matching project root path.When asking the user a question, use the platform's blocking question tool (AskUserQuestion in Claude Code, request_user_input in Codex, ask_user in Gemini). Fall back to numbered options in chat when no blocking tool is available. Ask one question at a time. Prefer concise single-select choices when natural options exist.
This skill follows the standard sf-compound-engineering execution discipline:
<feature_description> block above and any referenced files, plans, or issues.force-app/main/default/..., test commands like sf apex run test, deploy commands like sf project deploy validate and sf project deploy start, query the org with sf data query when state inspection is needed.docs/solutions/ (search via the sf-learnings-researcher agent).CLAUDE.md for frontmatter, naming, and protected-artifact rules.npx claudepluginhub gellasangameshgupta/salesforce-compound-engineering-plugin --plugin sf-compound-engineeringCreates bite-sized, testable implementation plans from specs or requirements, with file structure and task decomposition. Activates before coding multi-step tasks.