📦
jira-workflow
38承認ゲートでJiraワークフローを管理
Jiraの更新は開発作業からずれがちで、手動のフォローアップが必要になることがよくあります。このスキルは、Claude、Codex、またはClaude Codeがストーリーを提案し、承認を求め、課題を作成し、ワークフローステータスを同期するのを支援します。
生産性 表示
スキル jira-safe
📦
jira-safe
コンテンツリビジョン r1 高リスク ⚙️ 外部コマンド🌐 ネットワークアクセス🔑 環境変数📁 ファイルシステムへのアクセス
SAFe Jira ワークフローを整理する
Jira での SAFe 計画は、エピック、ストーリー、サブタスク全体で一貫性を保つのが困難です。このスキルは、Jira 課題の作成とワークフロー更新のための構造化されたテンプレートとスクリプトを提供します。
対応: Claude Codex Code(CC)
インストール前に停止して確認を求めてください。
計画を確認し、ファイルを変更する前にユーザーの明示的な同意を得てください。
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
エージェントリクエスト
Review the Skillstore skill "jira-safe" from https://skillstore.io/skills/01000001-01001110-jira-safe.md and its manifest at https://skillstore.io/api/skills/01000001-01001110-jira-safe/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「jira-safe」を使用しています。 チーム管理対象 Jira プロジェクトで、パスワードリセットのストーリーを作成してください。
期待される結果:
ペルソナ、目標、利点、Given-When-Then 形式の基準、完了の定義、推奨サブタスクを含む SAFe ストーリー。
「jira-safe」を使用しています。 マーケティングアシスタント製品の MVP バックログを計画してください。
期待される結果:
ビジネス成果、成功指標、グループ化されたストーリー、実装サブタスク、Jira のリンク付けガイダンスを含むエピック概要。
「jira-safe」を使用しています。 実装後に SCRUM-100 を To Do から Done に移動してください。
期待される結果:
利用可能な Jira 遷移を照会し、一致する状態を選択し、完了メモを追加して、更新を確認する遷移チェックリスト。
セキュリティ監査
高リスクv11 • 2026/7/7 バージョン別レポートを開く
The many command-execution and certificate findings are mostly false positives caused by Markdown backticks, JavaScript template literals, and Jira issue key fields. Real risks remain because the skill and scripts use Jira credentials, perform authenticated network writes, and include destructive bulk-delete guidance.
8
スキャンされたファイル
4,225
解析済み行数
78
レビュー項目
0
誤検知を無視
確認済みのセキュリティ上の懸念 (16)
高
Environment file access
const JIRA_EMAIL = process.env.JIRA_EMAIL;
The code reads JIRA_EMAIL as part of the Basic authentication credential pair. It is expected but still sensitive account-identifying data.
高
Environment file access
const JIRA_API_TOKEN = process.env.JIRA_API_TOKEN;
The code reads JIRA_API_TOKEN, a secret used to build Basic authentication for Jira API calls. Exposure or misuse of this token would affect the Jira account.
高
Environment file access
const JIRA_EMAIL = process.env.JIRA_EMAIL;
The code reads JIRA_EMAIL as part of the Basic authentication credential pair. It is expected but still sensitive account-identifying data.
高
Environment file access
const JIRA_API_TOKEN = process.env.JIRA_API_TOKEN;
The code reads JIRA_API_TOKEN, a secret used to build Basic authentication for Jira API calls. Exposure or misuse of this token would affect the Jira account.
高
Environment file access
# Load .env file from jira root (two levels up from scripts/)
The Python helper loads a parent .env file that can contain Jira credentials. Reading local environment files is a real sensitive-file access pattern.
高
Environment file access
env_path = Path(__file__).parent.parent.parent / '.env'
The Python helper loads a parent .env file that can contain Jira credentials. Reading local environment files is a real sensitive-file access pattern.
高
Environment file access
const JIRA_EMAIL = process.env.JIRA_EMAIL;
The code reads JIRA_EMAIL as part of the Basic authentication credential pair. It is expected but still sensitive account-identifying data.
高
Environment file access
const JIRA_API_TOKEN = process.env.JIRA_API_TOKEN;
The code reads JIRA_API_TOKEN, a secret used to build Basic authentication for Jira API calls. Exposure or misuse of this token would affect the Jira account.
確認済みの16件をすべて表示
高
Environment file access
# Load .env file from jira root (two levels up from scripts/)
The Python helper loads a parent .env file that can contain Jira credentials. Reading local environment files is a real sensitive-file access pattern.
高
Environment file access
env_path = Path(__file__).parent.parent.parent / '.env'
The Python helper loads a parent .env file that can contain Jira credentials. Reading local environment files is a real sensitive-file access pattern.
高
Environment file access
const JIRA_EMAIL = process.env.JIRA_EMAIL;
The code reads JIRA_EMAIL as part of the Basic authentication credential pair. It is expected but still sensitive account-identifying data.
高
Environment file access
const JIRA_API_TOKEN = process.env.JIRA_API_TOKEN;
The code reads JIRA_API_TOKEN, a secret used to build Basic authentication for Jira API calls. Exposure or misuse of this token would affect the Jira account.
高
Environment file access
# Load .env file from jira root (two levels up from scripts/)
The Python helper loads a parent .env file that can contain Jira credentials. Reading local environment files is a real sensitive-file access pattern.
高
Environment file access
env_path = Path(__file__).parent.parent.parent / '.env'
The Python helper loads a parent .env file that can contain Jira credentials. Reading local environment files is a real sensitive-file access pattern.
高
Destructive Jira Bulk Delete Helper
The skill documents a helper that searches all issues in a project and deletes each issue with deleteSubtasks=true. This can remove a large Jira backlog if copied or executed with a privileged token.
Lines 341-355 show a bulk delete routine that searches Jira issues and sends DELETE requests. The behavior is explicit and destructive, though it is documented rather than hidden.
中
Bulk Jira Issue Creation Without Interactive Confirmation
Executable scripts create epics, stories, and subtasks directly when run. They do not implement a dry-run or interactive confirmation step before writing to Jira.
The cited code calls createIssue for epics, stories, and subtasks in loops. No confirmation gate or dry-run branch is present in those execution paths.
機能レビュー項目 (78)
これらは、このスキルに期待される可能性のある実際のローカル機能であるため、レビューが必要ですが、確認済みの悪意ある動作としてはカウントされません。
高
Fetch API call
await fetch(`${JIRA_URL}/rest/api/3/issue/${issue.key}?deleteSubtasks=true`, {
This Jira API request performs DELETE against issue URLs with deleteSubtasks=true. It can remove project issues if executed with a privileged token.
中
Environment variable access (dot notation)
const JIRA_EMAIL = process.env.JIRA_EMAIL;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
中
Environment variable access (dot notation)
const JIRA_API_TOKEN = process.env.JIRA_API_TOKEN;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
中
Environment variable object
const JIRA_EMAIL = process.env.JIRA_EMAIL;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
中
Environment variable object
const JIRA_API_TOKEN = process.env.JIRA_API_TOKEN;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
中
Fetch API call
const response = await fetch(url, {
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
中
Fetch API call
const response = await fetch(url, {
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
中
Fetch API call
const response = await fetch(url, { headers });
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
中
Environment variable access (dot notation)
const JIRA_EMAIL = process.env.JIRA_EMAIL;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
中
Environment variable access (dot notation)
const JIRA_API_TOKEN = process.env.JIRA_API_TOKEN;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
中
Environment variable object
const JIRA_EMAIL = process.env.JIRA_EMAIL;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
中
Environment variable object
const JIRA_API_TOKEN = process.env.JIRA_API_TOKEN;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
中
HTTP client library
def make_request(method, path, data=None):
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
中
HTTP client library
return make_request('POST', '/issue', {'fields': fields})
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
中
HTTP client library
return make_request('POST', '/issue', {'fields': fields})
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
中
HTTP client library
return make_request('GET', f'/issue/{issue_key}?fields=summary,issuetype')
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
中
Python HTTP libraries
from urllib.request import Request, urlopen
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
中
Python environment access
os.environ.setdefault(key.strip(), value.strip())
This line loads values from a .env file into process environment variables. The surrounding block is used to provide Jira credentials to API calls.
中
Python environment access
JIRA_EMAIL = os.environ.get('JIRA_EMAIL')
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
中
Python environment access
JIRA_API_TOKEN = os.environ.get('JIRA_API_TOKEN')
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
中
Fetch API call
const response = await fetch(url, { ...options, headers });
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
中
Environment variable access (dot notation)
const JIRA_EMAIL = process.env.JIRA_EMAIL;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
中
Environment variable access (dot notation)
const JIRA_API_TOKEN = process.env.JIRA_API_TOKEN;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
中
Environment variable object
const JIRA_EMAIL = process.env.JIRA_EMAIL;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
中
Environment variable object
const JIRA_API_TOKEN = process.env.JIRA_API_TOKEN;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
中
HTTP client library
def jira_request(path, method='GET', data=None):
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
中
HTTP client library
return jira_request('/issue', method='POST', data={'fields': fields})
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
中
Python HTTP libraries
from urllib.request import Request, urlopen
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
中
Python environment access
os.environ.setdefault(key.strip(), value.strip())
This line loads values from a .env file into process environment variables. The surrounding block is used to provide Jira credentials to API calls.
中
Python environment access
JIRA_EMAIL = os.environ.get('JIRA_EMAIL')
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
中
Python environment access
JIRA_API_TOKEN = os.environ.get('JIRA_API_TOKEN')
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
中
Fetch API call
const response = await fetch(`${JIRA_BASE_URL}/rest/api/3/issue`, {
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
中
Environment variable access (dot notation)
const JIRA_EMAIL = process.env.JIRA_EMAIL;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
中
Environment variable access (dot notation)
const JIRA_API_TOKEN = process.env.JIRA_API_TOKEN;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
中
Environment variable object
const JIRA_EMAIL = process.env.JIRA_EMAIL;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
中
Environment variable object
const JIRA_API_TOKEN = process.env.JIRA_API_TOKEN;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
中
HTTP client library
def make_request(method, path, data=None):
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
中
HTTP client library
return make_request('POST', '/issue', {'fields': fields})
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
中
Python HTTP libraries
from urllib.request import Request, urlopen
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
中
Python environment access
os.environ.setdefault(key.strip(), value.strip())
This line loads values from a .env file into process environment variables. The surrounding block is used to provide Jira credentials to API calls.
中
Python environment access
JIRA_EMAIL = os.environ.get('JIRA_EMAIL')
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
中
Python environment access
JIRA_API_TOKEN = os.environ.get('JIRA_API_TOKEN')
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
低
Fetch API call
const response = await fetch(`${JIRA_BASE_URL}/rest/api/3/issue`, {
The skill documents authenticated Jira REST calls as part of its intended workflow. This is legitimate functionality but still a real external network side effect.
低
Fetch API call
const response = await fetch(`${JIRA_BASE_URL}/rest/api/3/issue`, {
The skill documents authenticated Jira REST calls as part of its intended workflow. This is legitimate functionality but still a real external network side effect.
低
Fetch API call
const response = await fetch(
The skill documents authenticated Jira REST calls as part of its intended workflow. This is legitimate functionality but still a real external network side effect.
低
Fetch API call
const response = await fetch(
The skill documents authenticated Jira REST calls as part of its intended workflow. This is legitimate functionality but still a real external network side effect.
低
Fetch API call
const response = await fetch(
The skill documents authenticated Jira REST calls as part of its intended workflow. This is legitimate functionality but still a real external network side effect.
低
Fetch API call
const response = await fetch(
The skill documents authenticated Jira REST calls as part of its intended workflow. This is legitimate functionality but still a real external network side effect.
低
Environment variable access (dot notation)
const JIRA_BASE_URL = process.env.JIRA_BASE_URL;
The code reads the Jira base URL from the environment and later sends authenticated requests to that destination. This is configuration, but it affects credential exposure boundaries.
低
Environment variable access (dot notation)
const PROJECT_KEY = process.env.JIRA_PROJECT_KEY;
The project key is not secret, but it controls which Jira project receives write operations. Misconfiguration can direct automation to the wrong project.
低
Environment variable object
const JIRA_BASE_URL = process.env.JIRA_BASE_URL;
The code reads the Jira base URL from the environment and later sends authenticated requests to that destination. This is configuration, but it affects credential exposure boundaries.
低
Environment variable object
const PROJECT_KEY = process.env.JIRA_PROJECT_KEY;
The project key is not secret, but it controls which Jira project receives write operations. Misconfiguration can direct automation to the wrong project.
低
Environment variable access (dot notation)
const JIRA_BASE_URL = process.env.JIRA_BASE_URL;
The code reads the Jira base URL from the environment and later sends authenticated requests to that destination. This is configuration, but it affects credential exposure boundaries.
低
Environment variable access (dot notation)
const PROJECT_KEY = process.env.JIRA_PROJECT_KEY || 'SCRUM';
The project key is not secret, but it controls which Jira project receives write operations. Misconfiguration can direct automation to the wrong project.
低
Environment variable object
const JIRA_BASE_URL = process.env.JIRA_BASE_URL;
The code reads the Jira base URL from the environment and later sends authenticated requests to that destination. This is configuration, but it affects credential exposure boundaries.
低
Environment variable object
const PROJECT_KEY = process.env.JIRA_PROJECT_KEY || 'SCRUM';
The project key is not secret, but it controls which Jira project receives write operations. Misconfiguration can direct automation to the wrong project.
低
Python environment access
JIRA_BASE_URL = os.environ.get('JIRA_BASE_URL')
The code reads the Jira base URL from the environment and later sends authenticated requests to that destination. This is configuration, but it affects credential exposure boundaries.
低
Python environment access
PROJECT_KEY = os.environ.get('JIRA_PROJECT_KEY', 'SCRUM')
The project key is not secret, but it controls which Jira project receives write operations. Misconfiguration can direct automation to the wrong project.
低
Environment variable access (dot notation)
const JIRA_BASE_URL = process.env.JIRA_BASE_URL;
The code reads the Jira base URL from the environment and later sends authenticated requests to that destination. This is configuration, but it affects credential exposure boundaries.
低
Environment variable access (dot notation)
const PROJECT_KEY = process.env.JIRA_PROJECT_KEY || 'SCRUM';
The project key is not secret, but it controls which Jira project receives write operations. Misconfiguration can direct automation to the wrong project.
低
Environment variable object
const JIRA_BASE_URL = process.env.JIRA_BASE_URL;
The code reads the Jira base URL from the environment and later sends authenticated requests to that destination. This is configuration, but it affects credential exposure boundaries.
低
Environment variable object
const PROJECT_KEY = process.env.JIRA_PROJECT_KEY || 'SCRUM';
The project key is not secret, but it controls which Jira project receives write operations. Misconfiguration can direct automation to the wrong project.
低
Python environment access
JIRA_BASE_URL = os.environ.get('JIRA_BASE_URL')
The code reads the Jira base URL from the environment and later sends authenticated requests to that destination. This is configuration, but it affects credential exposure boundaries.
低
Python environment access
PROJECT_KEY = os.environ.get('JIRA_PROJECT_KEY', 'SCRUM')
The project key is not secret, but it controls which Jira project receives write operations. Misconfiguration can direct automation to the wrong project.
低
Environment variable access (dot notation)
const JIRA_BASE_URL = process.env.JIRA_BASE_URL;
The code reads the Jira base URL from the environment and later sends authenticated requests to that destination. This is configuration, but it affects credential exposure boundaries.
低
Environment variable access (dot notation)
const PROJECT_KEY = process.env.JIRA_PROJECT_KEY || 'SCRUM';
The project key is not secret, but it controls which Jira project receives write operations. Misconfiguration can direct automation to the wrong project.
低
Environment variable object
const JIRA_BASE_URL = process.env.JIRA_BASE_URL;
The code reads the Jira base URL from the environment and later sends authenticated requests to that destination. This is configuration, but it affects credential exposure boundaries.
低
Environment variable object
const PROJECT_KEY = process.env.JIRA_PROJECT_KEY || 'SCRUM';
The project key is not secret, but it controls which Jira project receives write operations. Misconfiguration can direct automation to the wrong project.
低
Python environment access
JIRA_BASE_URL = os.environ.get('JIRA_BASE_URL')
The code reads the Jira base URL from the environment and later sends authenticated requests to that destination. This is configuration, but it affects credential exposure boundaries.
低
Python environment access
PROJECT_KEY = os.environ.get('JIRA_PROJECT_KEY', 'SCRUM')
The project key is not secret, but it controls which Jira project receives write operations. Misconfiguration can direct automation to the wrong project.
低
Fetch API call
const projectInfo = await fetch(`${JIRA_URL}/rest/api/3/project/${PROJECT_KEY}`, { headers });
The skill documents authenticated Jira REST calls as part of its intended workflow. This is legitimate functionality but still a real external network side effect.
低
Fetch API call
const epicResponse = await fetch(`${JIRA_URL}/rest/api/3/issue`, {
The skill documents authenticated Jira REST calls as part of its intended workflow. This is legitimate functionality but still a real external network side effect.
低
Fetch API call
const storyResponse = await fetch(`${JIRA_URL}/rest/api/3/issue`, {
The skill documents authenticated Jira REST calls as part of its intended workflow. This is legitimate functionality but still a real external network side effect.
低
Fetch API call
const storyResponse = await fetch(`${JIRA_URL}/rest/api/3/issue`, {
The skill documents authenticated Jira REST calls as part of its intended workflow. This is legitimate functionality but still a real external network side effect.
低
Fetch API call
const subtaskResponse = await fetch(`${JIRA_URL}/rest/api/3/issue`, {
The skill documents authenticated Jira REST calls as part of its intended workflow. This is legitimate functionality but still a real external network side effect.
低
Fetch API call
const response = await fetch(`${JIRA_URL}/rest/api/3/field`, { headers });
The skill documents authenticated Jira REST calls as part of its intended workflow. This is legitimate functionality but still a real external network side effect.
低
Fetch API call
const searchResponse = await fetch(
The skill documents authenticated Jira REST calls as part of its intended workflow. This is legitimate functionality but still a real external network side effect.
低
Fetch API call
const response = await fetch(url, { ...options, headers });
The skill documents authenticated Jira REST calls as part of its intended workflow. This is legitimate functionality but still a real external network side effect.
リスク要因
⚙️ 外部コマンド (207)
jira-workflow/SKILL.md:11 jira-workflow/SKILL.md:12 jira-workflow/SKILL.md:13 jira-workflow/SKILL.md:14 jira-workflow/SKILL.md:15 jira-workflow/SKILL.md:17 jira-workflow/SKILL.md:31-37 jira-workflow/SKILL.md:37-41 jira-workflow/SKILL.md:41-42 jira-workflow/SKILL.md:42-50 jira-workflow/SKILL.md:50-64 jira-workflow/SKILL.md:64-74 jira-workflow/SKILL.md:74-77 jira-workflow/SKILL.md:77-79 jira-workflow/SKILL.md:79-101 jira-workflow/SKILL.md:101-109 jira-workflow/SKILL.md:109-137 jira-workflow/SKILL.md:137-145 jira-workflow/SKILL.md:145-151 jira-workflow/SKILL.md:151-153 jira-workflow/SKILL.md:153-174 jira-workflow/SKILL.md:174-182 jira-workflow/SKILL.md:182-186 jira-workflow/SKILL.md:186-209 jira-workflow/SKILL.md:209-217 jira-workflow/SKILL.md:217-226 jira-workflow/SKILL.md:226-230 jira-workflow/SKILL.md:230-256 jira-workflow/SKILL.md:256-261 jira-workflow/SKILL.md:261-262 jira-workflow/SKILL.md:262-263 jira-workflow/SKILL.md:263-278 jira-workflow/SKILL.md:278-300 jira-workflow/SKILL.md:300-308 jira-workflow/SKILL.md:308-311 jira-workflow/SKILL.md:311-316 jira-workflow/SKILL.md:316-322 jira-workflow/SKILL.md:322-326 jira-workflow/SKILL.md:326-338 jira-workflow/SKILL.md:338-339 jira-workflow/SKILL.md:339-340 jira-workflow/SKILL.md:340-345 jira-workflow/SKILL.md:345-355 jira-workflow/SKILL.md:355-358 jira-workflow/SKILL.md:358-361 jira-workflow/SKILL.md:361-365 jira-workflow/SKILL.md:365-369 jira-workflow/SKILL.md:369-375 jira-workflow/SKILL.md:375-381 jira-workflow/SKILL.md:381-387 jira-workflow/SKILL.md:387-389 jira-workflow/SKILL.md:389-397 jira-workflow/SKILL.md:397-413 jira-workflow/SKILL.md:413-422 jira-workflow/SKILL.md:422-425 jira-workflow/SKILL.md:425-428 jira-workflow/SKILL.md:428-432 jira-workflow/SKILL.md:432-436 jira-workflow/SKILL.md:436-475 jira-workflow/SKILL.md:475-485 jira-workflow/SKILL.md:485-493 jira-workflow/SKILL.md:493-508 jira-workflow/SKILL.md:508-528 jira-workflow/SKILL.md:528-538 jira-workflow/SKILL.md:538-551 jira-workflow/SKILL.md:551-555 jira-workflow/SKILL.md:555-580 jira-workflow/SKILL.md:580-604 jira-workflow/SKILL.md:604-605 jira-workflow/SKILL.md:605-606 jira-workflow/SKILL.md:606-607 jira-workflow/SKILL.md:607-608 jira-workflow/SKILL.md:608-609 jira-workflow/SKILL.md:609-610 jira-workflow/SKILL.md:610-611 jira-workflow/SKILL.md:611-623 jira-workflow/SKILL.md:623-628 jira-workflow/SKILL.md:628-647 jira-workflow/SKILL.md:647-657 jira-workflow/SKILL.md:657-665 jira-workflow/SKILL.md:665-669 jira-workflow/SKILL.md:669-683 jira-workflow/SKILL.md:683-689 jira-workflow/SKILL.md:689 jira-workflow/SKILL.md:690 jira-workflow/SKILL.md:691 jira-workflow/SKILL.md:692 scripts/add-subtasks.mjs:20 scripts/add-subtasks.mjs:23 scripts/add-subtasks.mjs:34 scripts/add-subtasks.mjs:52 scripts/add-subtasks.mjs:60 scripts/add-subtasks.mjs:80 scripts/add-subtasks.mjs:88 scripts/add-subtasks.mjs:108 scripts/add-subtasks.mjs:119 scripts/add-subtasks.mjs:125 scripts/add-subtasks.mjs:128 scripts/add-subtasks.mjs:137 scripts/add-subtasks.mjs:138 scripts/add-subtasks.mjs:139 scripts/add-subtasks.mjs:140 scripts/add-subtasks.mjs:152 scripts/add-subtasks.mjs:156 scripts/add-subtasks.mjs:160 scripts/add-subtasks.mjs:161 scripts/add-subtasks.mjs:165 scripts/add-subtasks.mjs:169 scripts/add-subtasks.mjs:172 scripts/add-subtasks.mjs:181 scripts/add-subtasks.mjs:182 scripts/add-subtasks.mjs:183 scripts/add-subtasks.mjs:184 scripts/create-mvp.mjs:18 scripts/create-mvp.mjs:21 scripts/create-mvp.mjs:31 scripts/create-mvp.mjs:36 scripts/create-mvp.mjs:729 scripts/create-mvp.mjs:730 scripts/create-mvp.mjs:732 scripts/create-mvp.mjs:760 scripts/create-mvp.mjs:761 scripts/create-mvp.mjs:776 scripts/create-mvp.mjs:780 scripts/create-mvp.mjs:789 scripts/create-mvp.mjs:790 scripts/create-mvp.mjs:799 scripts/create-mvp.mjs:800 scripts/create-mvp.mjs:801 scripts/create-mvp.mjs:804 scripts/create-mvp.mjs:805 scripts/create-mvp.mjs:816 scripts/create-mvp.mjs:822 scripts/create-mvp.mjs:823 scripts/create-mvp.mjs:824 scripts/create-two-level.mjs:19 scripts/create-two-level.mjs:21 scripts/create-two-level.mjs:61 scripts/create-two-level.mjs:69 scripts/create-two-level.mjs:486 scripts/create-two-level.mjs:497 scripts/create-two-level.mjs:514 scripts/create-two-level.mjs:530 scripts/create-two-level.mjs:533 scripts/create-two-level.mjs:541 scripts/create-two-level.mjs:547 scripts/create-two-level.mjs:555 scripts/create-two-level.mjs:556 scripts/create-two-level.mjs:557 scripts/create-two-level.mjs:561 scripts/create-two-level.mjs:563 scripts/create-two-level.mjs:567 scripts/create-two-level.mjs:568 SKILL.md:24 SKILL.md:25 SKILL.md:26 SKILL.md:27 SKILL.md:30-31 SKILL.md:31-34 SKILL.md:34-38 SKILL.md:38-44 SKILL.md:44-50 SKILL.md:50-98 SKILL.md:98-102 SKILL.md:102-189 SKILL.md:189-193 SKILL.md:193-205 SKILL.md:205-211 SKILL.md:211-214 SKILL.md:214 SKILL.md:220-228 SKILL.md:228-232 SKILL.md:232-242 SKILL.md:242-250 SKILL.md:250-256 SKILL.md:256-264 SKILL.md:264-268 SKILL.md:268-271 SKILL.md:271 SKILL.md:284-291 SKILL.md:291-299 SKILL.md:299-321 SKILL.md:321-327 SKILL.md:327-329 SKILL.md:329-339 SKILL.md:339-343 SKILL.md:343-346 SKILL.md:346-348 SKILL.md:348-355 SKILL.md:355-359 SKILL.md:359-365 SKILL.md:365-370 SKILL.md:370-371 SKILL.md:371-382 SKILL.md:382-386 SKILL.md:386-389 SKILL.md:389-395 SKILL.md:395-401 SKILL.md:401-402 SKILL.md:402-409 SKILL.md:409-410 SKILL.md:410-417 SKILL.md:417-418 SKILL.md:418-419 SKILL.md:419-431 SKILL.md:431-437 SKILL.md:437-443
🌐 ネットワークアクセス (39)
jira-workflow/SKILL.md:174 jira-workflow/SKILL.md:209 jira-workflow/SKILL.md:310 jira-workflow/SKILL.md:344 jira-workflow/SKILL.md:412 jira-workflow/SKILL.md:474 jira-workflow/SKILL.md:34 jira-workflow/SKILL.md:698 jira-workflow/SKILL.md:699 jira-workflow/SKILL.md:700 jira-workflow/SKILL.md:701 scripts/add-subtasks.mjs:44 scripts/add-subtasks.mjs:72 scripts/add-subtasks.mjs:89 scripts/add-subtasks.py:61 scripts/add-subtasks.py:86 scripts/add-subtasks.py:100 scripts/add-subtasks.py:106 scripts/add-subtasks.py:21 scripts/create-mvp.mjs:32 scripts/create-mvp.py:62 scripts/create-mvp.py:122 scripts/create-mvp.py:18 scripts/create-two-level.mjs:61 scripts/create-two-level.py:54 scripts/create-two-level.py:110 scripts/create-two-level.py:14 SKILL.md:31 SKILL.md:220 SKILL.md:242 SKILL.md:284 SKILL.md:299 SKILL.md:329 SKILL.md:347 SKILL.md:355 SKILL.md:433 SKILL.md:447 SKILL.md:448 SKILL.md:449
🔑 環境変数 (47)
jira-workflow/SKILL.md:146 jira-workflow/SKILL.md:147 jira-workflow/SKILL.md:148 jira-workflow/SKILL.md:149 jira-workflow/SKILL.md:146 jira-workflow/SKILL.md:147 jira-workflow/SKILL.md:148 jira-workflow/SKILL.md:149 scripts/add-subtasks.mjs:7 scripts/add-subtasks.mjs:8 scripts/add-subtasks.mjs:9 scripts/add-subtasks.mjs:10 scripts/add-subtasks.mjs:7 scripts/add-subtasks.mjs:8 scripts/add-subtasks.mjs:9 scripts/add-subtasks.mjs:10 scripts/add-subtasks.py:33 scripts/add-subtasks.py:38 scripts/add-subtasks.py:39 scripts/add-subtasks.py:40 scripts/add-subtasks.py:41 scripts/create-mvp.mjs:5 scripts/create-mvp.mjs:6 scripts/create-mvp.mjs:7 scripts/create-mvp.mjs:8 scripts/create-mvp.mjs:5 scripts/create-mvp.mjs:6 scripts/create-mvp.mjs:7 scripts/create-mvp.mjs:8 scripts/create-mvp.py:30 scripts/create-mvp.py:35 scripts/create-mvp.py:36 scripts/create-mvp.py:37 scripts/create-mvp.py:38 scripts/create-two-level.mjs:6 scripts/create-two-level.mjs:7 scripts/create-two-level.mjs:8 scripts/create-two-level.mjs:9 scripts/create-two-level.mjs:6 scripts/create-two-level.mjs:7 scripts/create-two-level.mjs:8 scripts/create-two-level.mjs:9 scripts/create-two-level.py:26 scripts/create-two-level.py:31 scripts/create-two-level.py:32 scripts/create-two-level.py:33 scripts/create-two-level.py:34
監査者: codex 監査履歴を表示 →
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/01000001-01001110-jira-safe/audits/11?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/01000001-01001110-jira-safe?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/01000001-01001110-jira-safe?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/01000001-01001110-jira-safe/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/01000001-01001110-jira-safe.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>学術引用 (APA · BibTeX · CFF)
APA形式の引用
01000001-01001110. (2026). jira-safe security audit report (audit version 11) [Author version unspecified]. Skillstore. https://skillstore.io/skills/01000001-01001110-jira-safe/audits/11BibTeX形式の引用
@techreport{01000001-01001110-01000001-01001110-jira-safe-2026,
author = {01000001-01001110},
title = {jira-safe security audit report (audit version 11)},
institution = {Skillstore},
year = {2026},
number = {11},
url = {https://skillstore.io/skills/01000001-01001110-jira-safe/audits/11},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "jira-safe security audit report (audit version 11)"
version: "unspecified"
type: report
authors:
- name: "01000001-01001110"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/01000001-01001110-jira-safe/audits/11"
identifiers:
- type: other
value: "skillstore:01000001-01001110-jira-safe:audit:11"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中 45
アーキテクチャ
85
保守性
87
コンテンツ
73
コミュニティ
83
仕様準拠
作成できるもの
SAFe バックログを作成する
プロダクト要件を Jira のエピック、ストーリー、受け入れ基準、サブタスクに変換します。
スプリント作業を準備する
スプリント計画の前に、承認済みフィーチャーを実装ストーリーと技術サブタスクに分解します。
作業ステータスを同期する
Jira のワークフロー遷移パターンを使用して、課題を Progressing、review、Done の状態に進めます。
これらのプロンプトを試す
1 件のストーリーを作成する
このフィーチャーに対して SAFe ユーザーストーリーを 1 件作成してください。要約、ペルソナ、目標、利点、受け入れ基準、サブタスクを含めてください。
エピック計画を作成する
このプロダクト目標を、ビジネス成果、成功指標、ストーリー、実装サブタスクを含む 1 件の Jira エピックに変換してください。
Jira 作成手順を準備する
チーム管理対象プロジェクト向けに Jira 課題作成計画を準備してください。親リンクを示し、書き込み操作の前に確認してください。
ワークフロー自動化をレビューする
実行前に、この Jira ワークフロー自動化計画について、安全性、プロジェクトフィールドの互換性、レート制限、ロールバック手順をレビューしてください。
ベストプラクティス
- Jira 課題を作成または移動する前に、プロジェクトタイプと利用可能な遷移を確認します。
- 最小権限の Jira API トークンを使用し、まずサンドボックスプロジェクトでスクリプトをテストします。
- Jira への書き込み、削除、一括操作の前には、ユーザーの承認を求めます。
回避
- 生成されたバックログをレビューせずに、本番 Jira に対してデモスクリプトを実行すること。
- カスタムフィールド ID が Jira プロジェクト間で同一であると想定すること。
- ドライラン、許可リスト、入力による確認なしで一括削除ヘルパーを使用すること。
よくある質問
このスキルはチーム管理対象 Jira プロジェクトで機能しますか？
はい。例はチーム管理対象プロジェクトに重点を置き、エピックとストーリーの階層には parent フィールドを使用します。
Jira の認証情報は必要ですか？
はい。スクリプトと API の例には、Jira のメールアドレス、API トークン、ベース URL、プロジェクトキーの値が必要です。
実際の Jira 課題を作成できますか？
はい。含まれているスクリプトは、有効な認証情報で実行すると、エピック、ストーリー、サブタスクを作成できます。
ワークフロー状態を更新できますか？
はい。ワークフローのガイダンスでは、遷移を照会し、設定済みの Jira 状態間で課題を移動する方法を示します。
本番 Jira プロジェクトで安全に使用できますか？
注意が必要です。生成された作業をレビューし、最小権限のトークンを使用し、本番環境への書き込み前にはドライランまたはサンドボックスでのテストを推奨します。
カスタム Jira フィールドを自動的に処理しますか？
部分的に対応します。一般的なフィールドを説明し、検索ガイダンスも含みますが、各 Jira インスタンスで検証が必要になる場合があります。
開発者情報
ライセンス
MIT
Skillstore リビジョン
r1
バージョンに関する注意
作者はバージョンを宣言していません。
参照
7ed2830f0283f3a8900137d8dc893e54072206f3
メンテナンスの新しさ
2026/7/21
利用状況
83 ダウンロード · 405 閲覧
ファイル構成
01000001-01001110 のその他のスキル
すべて表示関連スキル
すべて表示📦
fusion-issue-authoring
81Draft and Publish Clear GitHub Issues
作成者 equinor
Unclear issue requests create rework, duplicates, and weak acceptance criteria. This skill produces reviewed GitHub issues with consistent structure and controlled publishing.
生産性 表示
📦
linear-projects-write
81CLI から Linear プロジェクトを管理
作成者 Bind
チームには、ツールを切り替えることなく Linear プロジェクトをすばやく一貫してセットアップする方法が必要です。このスキルは、Bun CLI を使って Linear プロジェクトを作成および更新する手順を Claude、Codex、Claude Code に案内します。
生産性 表示
📦
web-cli-teleport
81Claude Code Web と CLI を選択する
作成者 DNYoussef
タスクに対して誤った Claude Code インターフェースを選ぶと、チームは時間を失います。このスキルは Web、CLI、またはハイブリッドな引き継ぎワークフローを推奨します。
生産性 表示
📦
track-management
80Conductor トラックを整理する
作成者 sickn33
仕様、計画、ステータス、メタデータがばらばらになると、トラック作業は不明確になりがちです。このスキルは、Claude、Codex、Claude Code に Conductor track ワークフローのための構造化されたガイダンスを提供します。
生産性 表示
📦
lark-workflow-standup-report
80Lark スタンドアップレポートを生成
作成者 larksuite
会議とタスクが別々の Lark アプリに分かれていると、日々の計画に時間がかかります。このスキルは、カレンダーの予定と未完了タスクを 1 つのスタンドアップ用サマリーにまとめます。
生産性 表示
📦
linear-milestones-read
80CLI から Linear マイルストーンを読み取る
作成者 Bind
チームは、Web アプリを開かずに Linear マイルストーンをすばやく確認する必要があります。このスキルは、フィルタリングされたマイルストーン一覧のための読み取り専用 CLI ワークフローを実行します。
生産性 表示