bajutsu-e2e/bajutsu

japanese-document-writing

日本語の技術文書を執筆、翻訳、推敲するときに、Bajutsuの日本語文章規範を適用する。document-writingと併用する。

Source text: Japanese

document-writing

Apply Bajutsu's language-independent prose rules when writing or revising roadmap items or documentation. Use it with the matching English or Japanese writing skill.

japanese-document-writing

日本語の技術文書を執筆、翻訳、推敲するときに、Bajutsuの日本語文章規範を適用する。document-writingと併用する。

Source text: Japanese

document-writing

Apply Bajutsu's language-independent prose rules when writing or revising roadmap items or documentation. Use it with the matching English or Japanese writing skill.

english-document-writing

Apply Bajutsu's English prose mechanics when writing, translating, or revising English roadmap items and documentation. Use it together with document-writing.

english-document-writing

Apply Bajutsu's English prose mechanics when writing, translating, or revising English roadmap items and documentation. Use it together with document-writing.

ideation

Turn a rough Bajutsu feature idea into a bilingual roadmap proposal. Use for proposal authoring and review, never implementation.

ideation

Turn a rough Bajutsu feature idea into a bilingual roadmap proposal. Use for proposal authoring and review, never implementation.

implement-be

Implement an existing numbered Bajutsu Evolution roadmap item end to end, including tests, roadmap status, verification, a Draft PR, and follow-up.

implement-be

Implement an existing numbered Bajutsu Evolution roadmap item end to end, including tests, roadmap status, verification, a Draft PR, and follow-up.

fix-issue

Ship a plain GitHub issue — a small bug, papercut, or scoped improvement with no roadmap item — end to end, including tests, verification, a Draft PR, and follow-up.

fix-issue

Ship a plain GitHub issue — a small bug, papercut, or scoped improvement with no roadmap item — end to end, including tests, verification, a Draft PR, and follow-up.

investigate-ci-failure

Classify a pull request's failing CI checks — a mechanical gate slip, a real code defect, a known infrastructure flake, or something unclassified — with the evidence behind each verdict. Investigates and reports; never fixes, pushes, or re-runs.

investigate-scenario-flakiness

Rank a run history's scenarios by cross-run flakiness and, on request, diagnose why each flaky one flips — one read-only report from `bajutsu flakiness` plus an optional `bajutsu triage --flaky` pass.

pr-followup

Fix CI failures, address review comments, reply with grounds, and resolve conversations after a PR is opened.

investigate-ci-failure

Classify a pull request's failing CI checks — a mechanical gate slip, a real code defect, a known infrastructure flake, or something unclassified — with the evidence behind each verdict. Investigates and reports; never fixes, pushes, or re-runs.

investigate-scenario-flakiness

Rank a run history's scenarios by cross-run flakiness and, on request, diagnose why each flaky one flips — one read-only report from `bajutsu flakiness` plus an optional `bajutsu triage --flaky` pass.

pr-followup

Fix CI failures, address review comments, reply with grounds, and resolve conversations after a PR is opened.

record-issue

File a minor bug or a small, bounded improvement as a GitHub Issue — classify the finding, search for a duplicate, draft from this repository's issue templates, and create it only after explicit approval.

record-issue

File a minor bug or a small, bounded improvement as a GitHub Issue — classify the finding, search for a duplicate, draft from this repository's issue templates, and create it only after explicit approval.

cleanup

Clean up completed worktrees and merged branches after confirmation. Use when the user asks to remove stale worktrees or branches.

roadmap-filter

Find Bajutsu roadmap items by status, keyword, topic, or id. Use for read-only roadmap surveys, "is there already an item about X", and path lookup.

be-progress-tracker

Create or update a per-BE-item status Artifact (overview, implementation progress, work log). Called by ideation, implement-be, or propose-and-build at their own step boundaries — not run standalone.

claude-review

Judge a working diff or pull request against this repo's CI review contract (.github/claude-review-prompt.md) — the same judgment the "Claude review" GitHub Actions workflow applies. Classifies findings; never edits files.

git-sync

Fetch origin/main, rebase the current branch, and optionally prepare a topic worktree. Use for repository synchronization and worktree setup only.

propose-and-build

Author a small, well-scoped Bajutsu Evolution proposal and its implementation together in one PR.

task-select

Rank candidate Bajutsu tasks from GitHub Issues and the roadmap. Use when the user says "次のタスクを検討して", "タスクを選定して", "次に進めるべきタスクを", or asks to pick the next item to work on. Read-only — it never implements, creates branches, or opens PRs.

be-progress-tracker

Create or update a per-BE-item status Artifact (overview, implementation progress, work log). Called by ideation, implement-be, or propose-and-build at their own step boundaries — not run standalone.

claude-review

Judge a working diff or pull request against this repo's CI review contract (.github/claude-review-prompt.md) — the same judgment the "Claude review" GitHub Actions workflow applies. Classifies findings; never edits files.

propose-and-build

Author a small, well-scoped Bajutsu Evolution proposal and its implementation together in one PR.

task-select

Rank candidate Bajutsu tasks from GitHub Issues and the roadmap. Use when the user says "次のタスクを検討して", "タスクを選定して", "次に進めるべきタスクを", or asks to pick the next item to work on. Read-only — it never implements, creates branches, or opens PRs.