kiro-bootstrap/config.env at main · frankhefeng/kiro-bootstrap · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
# =============================================================================
# kiro-bootstrap configuration
# =============================================================================
# Edit this file, then run ./install.sh.
#
# Values marked "template" are substituted into the skill and steering copies
# the installer writes to ~/.kiro/ — the sources in this repo keep their
# {{PLACEHOLDER}} form, so re-running the installer after an edit is enough.
#
# To keep your own values out of git, copy this file to config.local.env: the
# installer prefers it when present, and it is gitignored.
#
# This is plain shell, sourced by install.sh. Do not put secrets here — tokens
# live in the macOS Keychain (see README).
# =============================================================================

# --- Atlassian ---------------------------------------------------------------
# Used by the jira and confluence skills.

# Atlassian Cloud hostname, no scheme. (template)
ATLASSIAN_SITE="example.atlassian.net"

# JIRA project key — the prefix in issue IDs such as PROJ-123. (template)
JIRA_PROJECT_KEY="PROJ"

# Numeric board ID, from the board URL. (template)
JIRA_BOARD_ID="1"

# Full board URL, quoted in generated reports. (template)
JIRA_BOARD_URL="https://example.atlassian.net/jira/software/c/projects/PROJ/boards/1"

# Default issue type when creating work items: Story, Task, or Bug. (template)
JIRA_DEFAULT_ISSUE_TYPE="Story"

# Story point custom field ID. Find yours with:
#   acli jira workitem view <KEY> --json | grep -i story
# 10016 is the common Jira Cloud default. (template)
JIRA_STORY_POINTS_FIELD="customfield_10016"

# Default Confluence space key. (template)
CONFLUENCE_SPACE_KEY="PROJ"

# Optional: enable the "Mermaid Diagrams Viewer" Forge app integration.
# This is the Atlassian Labs open-source viewer (one of several Mermaid plugins
# on the Marketplace):
#   https://marketplace.atlassian.com/apps/1231150/mermaid-macro-for-confluence
#   https://github.com/atlassian-labs/mermaid-diagrams-viewer
#
# When enabled, published pages get interactive viewer macros for each Mermaid
# code block. When disabled (default), Mermaid diagrams are published as plain
# fenced code blocks — still readable, just not interactive.
#
# To enable: set to true AND fill in the three site-specific IDs below. Find
# them by opening a page that already has a viewer macro → View Storage Format.
CONFLUENCE_MERMAID_VIEWER=false
CONFLUENCE_SITE_CLOUD_ID=""
CONFLUENCE_SPACE_ID=""
CONFLUENCE_CONTEXT_ID=""

# --- GitLab ------------------------------------------------------------------
# Used by the gitlab skill. Also the host checked for SSH and glab auth.

# Top-level group that scopes code search. (template)
GITLAB_GROUP="my-group"

# Instance hostname — gitlab.com, or your self-hosted host. (template)
GITLAB_HOSTNAME="gitlab.com"

# --- What to install ---------------------------------------------------------
# Everything in steering/, hooks/, and skills/ is installed as-is; curate by
# deleting the files you don't want from your clone. The switches below cover
# the parts that are not plain files in this repo.

# Apply datadog/pup-config.yaml to ~/.config/pup/config.yaml. This is the only
# path the installer writes outside ~/.kiro, because pup reads its config from
# nowhere else.
INSTALL_PUP_CONFIG=false

# AWS skills fetched from aws/agent-toolkit-for-aws at install time (needs
# Node.js). Set to "" to skip. Full list:
#   npx skills add aws/agent-toolkit-for-aws/skills/core-skills --list
AWS_SKILLS="aws-cdk aws-cloudformation aws-serverless aws-containers aws-compute"

# Datadog skills fetched from datadog-labs/agent-skills. Set to "" to skip.
DATADOG_SKILLS=""