Essential command-line tools and system utilities.
Self-improvement workflow after fixing any bug. Analyzes root causes and updates project guidance (CLAUDE.md, skills, commands) to prevent similar bugs. MUST be invoked after completing any bug fix before marking the fix as done.
Project Support Officer - Interface to the organization's project management system. Manages project list (project-list.csv), activity logs (project-activity-logs.csv), and project artifacts in org/projects/. Use when agents need to: create new projects, query project status, get active/all projects, record activity, save/get project artifacts, update project details, or close projects. All operations require caller identification (agent name/role). Only project managers can close projects. The PSO answers project-related questions and updates projects via scripts but does not perform non-project work.
Automated pull request review workflow. Fetch PR from GitHub, review with specialized agents (code quality, error handling, type safety, tests, documentation), post review comments, ask for approval before fixing issues, iterate until mergeable. Use when user asks to "review PR", "check pull request", "fix PR issues", or similar.
Display comprehensive project and session information including Git status, SPEC progress, version details, and system resources. Use when starting new sessions, checking project status, reviewing project context, or when users ask "what's the status", "show project info", or "where are we".
Quick overview of all projects (lightweight, Haiku-powered). Use to check project statuses, see what's active, or get a summary of all work. Triggers on "project status", "show projects", "what projects", "project overview".
Manage git worktrees for parallel branch development and PR reviews. Use when asked about: worktrees, working on multiple branches, parallel development, PR review without switching, testing without committing, multiple features simultaneously, long-running builds, comparing branches side-by-side. Integrates with: feature workflow, Azure DevOps work items, GitHub PRs.
This skill enables Telegram notifications for Claude Code sessions, alerting you when tasks complete. Use this when you want to walk away from your computer and be notified on your phone when Claude finishes or needs input.
Creates GitHub sub-issues and links them to parent issues using gh CLI and REST API. Use when creating child issues, breaking down large issues into smaller tasks, or establishing parent-child relationships between issues.
Analyzes why Buildkite pipeline steps were skipped, didn't run, or behaved unexpectedly. Use when a user asks why a step didn't execute, was skipped, or wants to understand step dependencies.
Manage GitHub Project board items - add issues, update status, move between columns. Use when user asks to add issues to board, change status, or organize the project.
This skill should be used when the user asks to "create issue", "search issues", "update ticket", "check notifications", mentions "Backlog", "バックログ", "課題", "チケット", discusses project management with Nulab Backlog, or needs to interact with Backlog API for issue tracking.
Knowledge about the context branch methodology for separating AI configuration from project code using git worktrees. Use when users ask about worktree structure, branch organization, or the separation of concerns pattern.
Complete CRUD for SDLC documentation (stories, tasks, context retrieval). Use when creating/managing stories, creating/managing tasks, updating task state, or retrieving full context for any user story via index (<3min restoration).
Generate GitHub issues from an approved engineering specification. Use to break down a spec into implementable, atomic tasks with dependencies, sizing, and labels.
Inspect GitHub PR checks with gh, pull failing GitHub Actions logs, summarize failure context, then create a fix plan and implement after user approval. Use when a user asks to debug or fix failing PR CI/CD checks on GitHub Actions and wants a plan + code changes; for external checks (e.g., Buildkite), only report the details URL and mark them out of scope.
Analyze GitHub Actions CI failures for the current branch. Use when the user asks about CI status, test failures, build errors, GitHub Actions problems, or mentions checking CI, workflow failures, or pipeline status.
Creates User Stories from UI screens using component-based decomposition. Analyzes screenshots or screen descriptions to identify UI components and generates User Stories with AMP acceptance criteria (Acceptance, Measure, Proof). Follows T-Minus-15 process template.
Dispatch milestones to user-facing timeline. Use when completing significant steps: starting major phases, calling external APIs, creating external references, completing database operations, or validating Pydantic models. Never dispatch every tool call or internal logs. Environment variables FULCRUM_DISPATCH_URL, FULCRUM_DISPATCH_TOKEN, FULCRUM_TICKET_UUID, and FULCRUM_RUN_UUID must be set (injected by system).
GitHub Issue resolver skill that analyzes, triages, and proposes solutions for issues with full SDD integration Trigger terms: resolve issue, fix issue, github issue, issue triage, issue analysis, issue to PR, issue resolution, auto-fix issue Use when: User requests involve GitHub issue analysis or resolution
Use this skill to start work on an assigned GitHub issue. This is the core implementation loop of the SynthesisFlow methodology. Guides the AI to load full context (specs, plans, retrospective), create a feature branch, and begin implementation. Triggers include "start work on issue", "implement issue
