From teams
Lists all OCPBUGS components, optionally filtered by team. Outputs JSON with component names and total count.
How this command is triggered — by the user, by Claude, or both
Slash command
/teams:list-components [--team <team-name>]The summary Claude sees in its command listing — used to decide when to auto-load this command
## Name teams:list-components ## Synopsis ## Description The `teams:list-components` command displays all OCPBUGS component names, with optional filtering by team. This command is useful for: - Discovering available OCPBUGS components - Discovering OCPBUGS components for a specific team - Validating OCPBUGS component names before filing or querying bugs - Understanding which components are tracked in OCPBUGS per team - Finding exact component names for use in JIRA queries ## Implementation 1. **Verify Working Directory** - Ensure you are in the repository root directory - Ru...
teams:list-components
/teams:list-components [--team <team-name>]
The teams:list-components command displays all OCPBUGS component names, with optional filtering by team.
This command is useful for:
Verify Working Directory
pwd to confirmRun the list-components Script
python3 plugins/teams/skills/list-components/list_components.pypython3 plugins/teams/skills/list-components/list_components.py --team "API Server"Parse and Display Results
List all OCPBUGS components:
/teams:list-components
List OCPBUGS components for a specific team:
/teams:list-components --team "API Server"
--team (optional): Filter components by team name
/teams:list-teams to get available team names--team "API Server"/teams:list-teams to get correct namesThe team and component mapping data originates from:
If data looks wrong or missing:
python3 plugins/teams/generate_team_component_map.py
team_component_map.json fileplugins/teams/skills/list-components/SKILL.md/teams:list-teamsplugins/teams/team_component_map.jsonplugins/teams/generate_team_component_map.pynpx claudepluginhub pavolloffay/ai-helpers --plugin teams/list-componentsLists all OCPBUGS components, optionally filtered by team. Outputs JSON with component names and total count.
/issues-by-componentLists and analyzes JIRA issues grouped by component with flexible filtering by time, assignee, reporter, status, and text search.
/teamAssembles and spawns multi-agent teams for parallel tasks, code reviews, security audits, and full-stack features. Supports create, context, and list subcommands.
/READMEProvides slash commands for the DevTeam multi-agent system, including planning, autonomous implementation, bug fixing, GitHub issue management, and code review.
/ep-watchMonitors open Enhancement PRs in the openshift/enhancements repository, filters out OLM team members, scores PRs for OLM relevance, and returns up to 3 impactful proposals.
/f5-teamManages team collaboration via sessions for joint development, multi-agent workflows like chain/parallel execution, and task handoffs with context preservation.