fvh-pre-commit
FVH (Forum Virium Helsinki) pre-commit hook standards and configuration. Use when configuring pre-commit hooks in FVH repositories, checking hook compliance, or when the user mentions FVH pre-commit, conventional commits, or hook configuration.
spec-flow-instructions
MUST use when working with spec files in `specs/` directories, or when commands reference this skill for conventions.
git-absorb
Automatically fold uncommitted changes into appropriate commits on a feature branch. Use when applying review feedback, fixing bugs in feature branches, or maintaining atomic commit history without manual interactive rebasing. Particularly useful for making corrections to recent commits without creating messy "fixes" commits.
gabb-code-navigation
Teaches when to use gabb_structure for efficient file exploration. Use gabb_structure before reading large files in supported languages.
project-status-sync
Use to keep GitHub Project fields synchronized with actual work state - updates status, verification, criteria counts, and other project-specific fields
task-startup
Comprehensive work session initialization orchestrator that validates environment, creates properly named branches, and prepares development environment for new tasks
forking-iteration
Use when user wants to create new autonomy branch from current commit or specific past iteration
session-start
Use at the beginning of every work session - establishes context by checking GitHub project state, reading memory, verifying environment, and orienting before starting work
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
plan-incremental-commits
Review a mixed working tree and produce (and optionally execute) a small, logically grouped sequence of incremental git commits.
github-tools
Executes GitHub operations via gh CLI wrapper. Use when managing issues, pull requests, workflows, CI runs, projects, releases, cache, labels, or searching repositories and code.
skill-refactoring
Refactor bloated skill.md files using progressive disclosure pattern. Moves detailed content to references/ while keeping skill.md focused and discoverable. Use when a skill is approaching 500 lines or needs better organization.
orchestrator
Issue/要件を受けたら分解→担当割当→実装→検証→統合を回す手順。未整備なら /repo-init でbootstrap。
git-operator
Manages Git operations including commits with appropriate conventions, combining related changes logically and following project-specific policies
brane-ship
Complete workflow for verifying and committing Brane SDK changes. Run after implementing fixes/features to verify impact, test affected modules, and prepare for commit.
start-issue
Start working on a GitHub issue. Use when the user wants to work on an issue, start an issue, or begin implementation.
deferred-finding
Use when a review finding cannot be fixed in current PR - creates properly documented tracking issue with full context, linked to parent, following full issue-driven-development process
threat-model-generation
Generate a STRIDE-based security threat model for a repository. Use when setting up security monitoring, after architecture changes, or for security audits.
memory-maintenance
Prune and consolidate state files, surface important items from journal to core state
