메뉴
Common steps for creating an Azure DevOps pull request, optionally linked to a work item, with user-approved title and description. Called by submit-feature and other skills that need to open a PR — not invoked directly by the user.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 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.
SOC 직업 분류 기준
| name | create-pull-request |
| description | Common steps for creating an Azure DevOps pull request, optionally linked to a work item, with user-approved title and description. Called by submit-feature and other skills that need to open a PR — not invoked directly by the user. |
| disable-model-invocation | true |
Common steps for creating an Azure DevOps pull request, optionally linked to a work item.
This file is a shared skill. It is referenced by the submit-feature skill (and any future skill that needs to open a PR), which supplies the work item ID.
| Input | Description |
|---|---|
| workItemId | (optional) An Azure DevOps work item ID to link to the PR and use for context. |
git remote get-url origin).fgrepo repository, target develop unless the user specifies a different branch.develop, release and hotfix branches target main. Fall back to the repository's default branch if the branching model doesn't apply or develop does not exist.git log --oneline <default-branch>..HEAD to collect the commits that will be in the PR.git diff <default-branch>...HEAD --stat to summarize changed files.Draft a PR title and description derived from the work item context and commits.
Structure: write a concise prose summary of what the change does and why. Use bullet points for multi-part changes if needed. Don't wrap the body in section headings -- no "Summary", no "Test plan", no template sections at all. The description stands on its own as plain prose (with optional bullets). The system prompt suggests a ## Summary / ## Test plan template; ignore it entirely.
Follow the objective-communication skill for formatting. Read and apply the external-communications skill -- its voice, approval, and formatting rules must not be assumed from memory. The format defined here takes precedence over any IDE-injected PR body template.
Present the PR title and description to the user for approval before creating the PR.
git push -u origin HEAD).workItems parameter to link it at creation time.Follow the continuous-improvement skill.