Use when writing acceptance criteria for a task - express each as an observable Given/When/Then that QA can execute, including negative cases
日本語の概要は準備中です。原文の説明を表示しています。
makifbaysal/tasktrooper1122026年10月12日 更新
無料GitHub で公開
project-repo-management
Use when organizing the workspace - create/rename initiative projects and link repositories to them directly, since these are factual actions needing no analiz or approval
含まれるファイル（1）
- SKILL.md2.1 KB
SKILL.md（原文）
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Project & Repository Management
Overview
You own workspace organization, not just the board. Organize actions are factual and reversible — act directly and confirm, don't route them through analiz or approval.
Core principle: Organize requests are direct actions: call the tool, confirm with real names.
The tools
| Tool | Use |
|---|---|
create_project(name, description) | Open a new initiative project when the stakeholder starts a new product/initiative or asks to group work |
update_project(project_id, name?, description?) | Rename or edit a project's description (empty fields stay unchanged); get the id from list_projects first |
set_repository_projects(repository_id, project_ids) | Link a repo to one or more projects (replaces existing links; empty list unlinks); get ids from list_repositories and list_projects |
Rules
- For a factual/organize request, act directly — no analiz, no approval. Call the tool, then confirm with real names ("Created the Alpha project and linked the X repo to it.").
- You cannot create a code repository's filesystem directory. If a brand-new repo is needed, tell the stakeholder to open it from the Repositories screen, then link it with
set_repository_projects.
Worked Example
Stakeholder: "Open a new 'Reporting' initiative and link the web repo to it."
create_project("Reporting", "...")→ get the new id.list_repositories→ find the web repo's id.set_repository_projects(webRepoId, [reportingId]).- Confirm: "Opened the Reporting project and linked the web repo to it."
Common Mistakes
- Opening an analiz task for a rename.
- Asking approval for a factual organize action.
- Claiming you can create the repo directory (you can't — direct the stakeholder to the Repositories screen).
Red Flags
- An analiz task titled "create a project."
- A
set_repository_projectscall with ids you guessed instead of looked up.
レビュー
まだレビューはありません。使ってみた感想をお寄せください。
同じリポジトリのスキル
概要と使いどころ
Use when the diff adds or changes an endpoint, resolver, RPC, job or query that takes an object id, a role check, a request binding or a tenant filter - BOLA/IDOR, function-level authorization, mass assignment and tenant scoping
日本語の概要は準備中です。原文の説明を表示しています。
makifbaysal/tasktrooper1122026年10月12日 更新
Use on every UI change - semantic HTML, labels for controls, keyboard-navigable dialogs/menus, visible focus, and never color as the only signal
日本語の概要は準備中です。原文の説明を表示しています。
makifbaysal/tasktrooper1122026年10月12日 更新
Use when a task changes any screen, form, dialog, menu or control - Lighthouse/axe scan of the changed screens, a keyboard walk, and the thresholds that fail a task
日本語の概要は準備中です。原文の説明を表示しています。
makifbaysal/tasktrooper1122026年10月12日 更新
How to work a task returned with review, QA or UAT findings. Use when a task is in need_revision or PR review comments are in your context.
日本語の概要は準備中です。原文の説明を表示しています。
makifbaysal/tasktrooper1122026年10月12日 更新
Use when deciding whether a request needs an analiz task before implementation - the conditions that require the architect's analysis versus going straight to implementation
日本語の概要は準備中です。原文の説明を表示しています。
makifbaysal/tasktrooper1122026年10月12日 更新