Agent Claude Code
Use this agent when the user explicitly requests data modeling assistance or asks to analyze data sources for creating storage schemas or reports. This agent should be invoked as a standalone task and is NOT meant to run proactively. Examples of when to use:\n\n \nuser: "Can you analyze our user database table and…
MCP server Claude CodeCodexCursor +2
One of 2 in .mcp.json
MCP server "Context7" as configured in Irata/ClaudeCode. Launched with cmd /c npx -y @upstash/context7-mcp.
Skill Claude Code
Record prompts and responses from the current Claude Code session into a structured conversation log.
Skill Claude Code
Bump the V.R.M version across the manifest XML and SQL update file for any Joomla extension project, verifying the manifest is wired to run schema updates.
Skill Claude Code
Summarise the commits on the current branch and write a markdown file suitable for pasting into a Pull Request description.
Skill Claude Code
Regenerate the dynamic include files (available-agents.md and available-skills.md) by scanning agent and skill directories for frontmatter.
Skill Claude Code
Scan the repository for file modifications and append structured daily entries to the project work log.
Skill Claude Code
Commit the working tree as scoped per-extension Conventional Commits, then merge to main, delete the branch and push.
MCP server Claude CodeCodexCursor +2
One of 2 in .mcp.json
MCP server "phpstorm", hosted remotely at 127.0.0.1, as configured in Irata/ClaudeCode.
Skill Claude Code
Audit a Joomla extension's language constants — missing, unused, malformed, duplicated and untranslated — including the messages Joomla builds implicitly from $textprefix.
Skill Claude Code
Bring a development Joomla instance's administrator menu into line with a component manifest's / — add new entries, remove stale ones, fix renamed keys and order — and confirm every menu language key resolves, without reinstalling the component.
Skill Claude Code
Consolidate every project's work log into one date-ordered table — date, day, project, work performed — with days worked per project per month, as the starting point for invoicing.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: