メニュー
Opens a pull request, links it to the feature work item, transitions the item to Code Review, and notifies the team on Slack. Use when submitting a feature for review, given a feature ID or a feature/<id> branch name.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | submit-feature |
| description | Opens a pull request, links it to the feature work item, transitions the item to Code Review, and notifies the team on Slack. Use when submitting a feature for review, given a feature ID or a feature/<id> branch name. |
| disable-model-invocation | true |
Given a feature ID (or inferred from the current branch name), open a pull request, link it to the work item, transition the work item to review, and notify the team on Slack.
Determine the feature ID using one of the following, in priority order:
git branch --show-current). If it matches the pattern feature/<id>, extract <id>.If neither yields a feature ID, ask the user and stop.
Run git status --porcelain to check for uncommitted changes (staged or unstaged).
Follow the create-pull-request skill, passing:
The shared skill will identify the repository, gather context, compose the description, and create the PR. Do not compose or present the Slack message yet -- the user may want to verify the PR live before notifying the team.
Update the work item state to Code Review.
When transitioning a Task, Azure DevOps requires CompletedWork to be non-empty. Set it to OriginalEstimate (or the actual hours spent) and RemainingWork to 0. Read these values from the work item fetched during PR creation.
This step begins only after the PR has been created and the link presented in step 3. Do not batch this approval with the PR approval -- they are separate interactions.
Read and apply the external-communications skill before composing any message in this step.
Defaults:
fundguard.slack.comhttps://fundguard.slack.com/archives/<channel_id>/p<ts_without_dot>When the user asks to share/send a message to a person by name, look up their Slack user ID via slack_get_users. Paginate through all pages using the cursor parameter until the user is found or all pages are exhausted. Do not stop after the first page.
Compose a message for the #team-cinfra Slack channel, following the objective-communication and external-communications skills. The message should include:
Present the Slack message to the user for approval before posting.
After the channel message is posted, check whether the PR touches agent artifacts. Skip this sub-step entirely if the repository is not fgrepo.
Run git diff <default-branch>...HEAD --name-only and review the changed file list. A file is an agent artifact if it matches any of the known patterns below or if it looks like an agent artifact by name or context.
Known patterns:
.cursor/**.claude/****/AGENTS.md, **/CLAUDE.md**/RULE-INDEX***/SKILL.md.cursorrules, .github/copilot-instructions.md, .gemini/**Also flag any file whose purpose is to instruct or configure an AI agent -- prompt templates, LLM system instructions, agent workflow definitions, MCP server configuration, AI-related config files, etc. Use judgment; when uncertain, include rather than exclude.
If agent artifacts are detected, compose a DM to Yaakov Ellis (Slack user ID U08NR4YBWTS) with a link to the PR and a note that it includes agent artifact changes. Follow the objective-communication skill and external-communications skill. Present the DM for user approval before sending.
After the channel message is posted, check whether the PR touches the automation/ directory. Skip this sub-step entirely if the repository is not fgrepo.
Using the same git diff <default-branch>...HEAD --name-only output from above, check whether any file path starts with automation/. If automation files are detected, compose a message for the automation support Slack channel (C03MVU629EG) with:
Follow the objective-communication skill and the external-communications skill. Present the message for user approval before posting.
Print a summary of everything that was done:
Follow the artifact-discovery skill. If the branch diff is non-trivial, present any suggestions to the user. The user can act on them later -- this step does not block submission.
Follow the continuous-improvement skill.
Deeply gather context from an Azure DevOps work item by following its relations, linked PRs, hyperlinks, and comments. Use whenever a command needs the full picture behind a work item -- planning features, reviewing PRs, triaging, or estimating.
Common steps for creating a new Azure DevOps work item in the FundGuard project, including iteration assignment, parent linking, and triage. Called by create-task, create-bug, and request-environment-access skills — not invoked directly by the user.
Mechanical estimate-and-transition of an Azure DevOps work item to the Triaged state. Called programmatically by skills that create or triage work items -- not invoked directly by the user. For user-initiated triage, use the triage skill instead.
Transitions an Azure DevOps work item to the Active state. Use when starting work on a work item, given an explicit ID or one inferred from the current feature branch.
Marks an Azure DevOps work item as Blocked and links it to its predecessor blocker. Use when a work item cannot proceed until another work item is completed.
Investigates bugs to find root cause, designs a TDD-based fix plan, and implements after approval. Use when given a bug ticket or description of defective behaviour that needs investigation and fixing in the codebase.