chief-clancy 0.5.2 → 0.5.4

package/dist/types/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/types/index.ts"],"names":[],"mappings":"AAAA,YAAY,EAAE,aAAa,EAAE,MAAM,EAAE,MAAM,YAAY,CAAC;AACxD,YAAY,EACV,WAAW,EACX,SAAS,EACT,OAAO,EACP,SAAS,EACT,SAAS,GACV,MAAM,kBAAkB,CAAC"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/types/index.ts"],"names":[],"mappings":"AAAA,YAAY,EAAE,aAAa,EAAE,MAAM,EAAE,MAAM,YAAY,CAAC;AACxD,YAAY,EACV,WAAW,EACX,gBAAgB,EAChB,cAAc,EACd,UAAU,GACX,MAAM,aAAa,CAAC;AACrB,YAAY,EACV,WAAW,EACX,SAAS,EACT,OAAO,EACP,SAAS,EACT,SAAS,GACV,MAAM,kBAAkB,CAAC"}

package/dist/types/remote.d.ts

@@ -0,0 +1,44 @@
+/**
+ * Remote git hosting types shared across remote detection and PR creation.
+ */
+/** Supported git hosting platforms. */
+export type GitPlatform = 'github' | 'gitlab' | 'bitbucket' | 'bitbucket-server' | 'azure' | 'unknown';
+/** Parsed remote URL with platform and path info. */
+export type RemoteInfo = {
+    host: 'github';
+    owner: string;
+    repo: string;
+    hostname: string;
+} | {
+    host: 'gitlab';
+    projectPath: string;
+    hostname: string;
+} | {
+    host: 'bitbucket';
+    workspace: string;
+    repoSlug: string;
+    hostname: string;
+} | {
+    host: 'bitbucket-server';
+    projectKey: string;
+    repoSlug: string;
+    hostname: string;
+} | {
+    host: 'azure' | 'unknown';
+    url: string;
+} | {
+    host: 'none';
+};
+/** Result of a PR/MR creation attempt. */
+export type PrCreationResult = {
+    ok: true;
+    url: string;
+    number: number;
+} | {
+    ok: false;
+    error: string;
+    alreadyExists?: boolean;
+};
+/** Progress log status values. */
+export type ProgressStatus = 'DONE' | 'SKIPPED' | 'PR_CREATED' | 'PUSHED' | 'PUSH_FAILED' | 'LOCAL' | 'PLAN' | 'APPROVE' | 'REWORK';
+//# sourceMappingURL=remote.d.ts.map

package/dist/types/remote.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"remote.d.ts","sourceRoot":"","sources":["../../src/types/remote.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH,uCAAuC;AACvC,MAAM,MAAM,WAAW,GACnB,QAAQ,GACR,QAAQ,GACR,WAAW,GACX,kBAAkB,GAClB,OAAO,GACP,SAAS,CAAC;AAEd,qDAAqD;AACrD,MAAM,MAAM,UAAU,GAClB;IACE,IAAI,EAAE,QAAQ,CAAC;IACf,KAAK,EAAE,MAAM,CAAC;IACd,IAAI,EAAE,MAAM,CAAC;IACb,QAAQ,EAAE,MAAM,CAAC;CAClB,GACD;IACE,IAAI,EAAE,QAAQ,CAAC;IACf,WAAW,EAAE,MAAM,CAAC;IACpB,QAAQ,EAAE,MAAM,CAAC;CAClB,GACD;IACE,IAAI,EAAE,WAAW,CAAC;IAClB,SAAS,EAAE,MAAM,CAAC;IAClB,QAAQ,EAAE,MAAM,CAAC;IACjB,QAAQ,EAAE,MAAM,CAAC;CAClB,GACD;IACE,IAAI,EAAE,kBAAkB,CAAC;IACzB,UAAU,EAAE,MAAM,CAAC;IACnB,QAAQ,EAAE,MAAM,CAAC;IACjB,QAAQ,EAAE,MAAM,CAAC;CAClB,GACD;IACE,IAAI,EAAE,OAAO,GAAG,SAAS,CAAC;IAC1B,GAAG,EAAE,MAAM,CAAC;CACb,GACD;IACE,IAAI,EAAE,MAAM,CAAC;CACd,CAAC;AAEN,0CAA0C;AAC1C,MAAM,MAAM,gBAAgB,GACxB;IAAE,EAAE,EAAE,IAAI,CAAC;IAAC,GAAG,EAAE,MAAM,CAAC;IAAC,MAAM,EAAE,MAAM,CAAA;CAAE,GACzC;IAAE,EAAE,EAAE,KAAK,CAAC;IAAC,KAAK,EAAE,MAAM,CAAC;IAAC,aAAa,CAAC,EAAE,OAAO,CAAA;CAAE,CAAC;AAE1D,kCAAkC;AAClC,MAAM,MAAM,cAAc,GACtB,MAAM,GACN,SAAS,GACT,YAAY,GACZ,QAAQ,GACR,aAAa,GACb,OAAO,GACP,MAAM,GACN,SAAS,GACT,QAAQ,CAAC"}

package/dist/types/remote.js

@@ -0,0 +1,5 @@
+/**
+ * Remote git hosting types shared across remote detection and PR creation.
+ */
+export {};
+//# sourceMappingURL=remote.js.map

package/dist/types/remote.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"remote.js","sourceRoot":"","sources":["../../src/types/remote.ts"],"names":[],"mappings":"AAAA;;GAEG"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "chief-clancy",
-  "version": "0.5.2",
+  "version": "0.5.4",
   "description": "Autonomous, board-driven development for Claude Code — scaffolds docs, integrates Kanban boards, runs tickets in a loop.",
   "keywords": [
     "claude",

package/src/roles/planner/workflows/plan.md

@@ -73,11 +73,17 @@ Note: include the `comment` field so we can check for existing plans and read fe
 
 ### GitHub Issues
 
+First resolve the authenticated username (don't use `@me` — it breaks with fine-grained PATs):
+```bash
+GITHUB_USERNAME=$(curl -s -H "Authorization: Bearer $GITHUB_TOKEN" https://api.github.com/user | jq -r '.login')
+```
+
+Then fetch issues:
 ```bash
 RESPONSE=$(curl -s \
   -H "Authorization: Bearer $GITHUB_TOKEN" \
   -H "X-GitHub-Api-Version: 2022-11-28" \
-  "https://api.github.com/repos/$GITHUB_REPO/issues?state=open&assignee=@me&labels=$CLANCY_PLAN_LABEL&per_page=<N>")
+  "https://api.github.com/repos/$GITHUB_REPO/issues?state=open&assignee=$GITHUB_USERNAME&labels=$CLANCY_PLAN_LABEL&per_page=<N>")
 ```
 
 - `CLANCY_PLAN_LABEL` defaults to `needs-refinement` if not set

package/src/roles/reviewer/workflows/review.md

@@ -41,7 +41,9 @@ RESPONSE=$(curl -s \
   -d '{"jql": "<jql as above>", "maxResults": 1, "fields": ["summary", "description", "issuelinks", "parent", "customfield_10014"]}')
 ```
 
-**GitHub Issues:** `GET /repos/$GITHUB_REPO/issues?state=open&assignee=@me&labels=clancy&per_page=1` — filter out PRs (entries with `pull_request` key)
+**GitHub Issues:** First resolve the authenticated username (don't use `@me` — it breaks with fine-grained PATs):
+`GITHUB_USERNAME=$(curl -s -H "Authorization: Bearer $GITHUB_TOKEN" https://api.github.com/user | jq -r '.login')`
+Then: `GET /repos/$GITHUB_REPO/issues?state=open&assignee=$GITHUB_USERNAME&labels=clancy&per_page=1` — filter out PRs (entries with `pull_request` key).
 
 **Linear:** GraphQL `viewer.assignedIssues` with `filter: { state: { type: { eq: "unstarted" } }, team: { id: { eq: "$LINEAR_TEAM_ID" } }[, labels: { name: { eq: "$CLANCY_LABEL" } }] }` (label clause only if `CLANCY_LABEL` is set), `first: 1`, `orderBy: priority`
 

package/src/roles/reviewer/workflows/status.md

@@ -42,11 +42,16 @@ RESPONSE=$(curl -s \
 ```
 
 **GitHub Issues:**
+First resolve the authenticated username (don't use `@me` — it breaks with fine-grained PATs):
+```bash
+GITHUB_USERNAME=$(curl -s -H "Authorization: Bearer $GITHUB_TOKEN" https://api.github.com/user | jq -r '.login')
+```
+Then fetch issues:
 ```bash
 RESPONSE=$(curl -s \
   -H "Authorization: Bearer $GITHUB_TOKEN" \
   -H "X-GitHub-Api-Version: 2022-11-28" \
-  "https://api.github.com/repos/$GITHUB_REPO/issues?state=open&assignee=@me&labels=clancy&per_page=3")
+  "https://api.github.com/repos/$GITHUB_REPO/issues?state=open&assignee=$GITHUB_USERNAME&labels=clancy&per_page=3")
 # Filter out PRs (entries with pull_request key)
 ```
 

package/src/roles/setup/workflows/init.md

@@ -207,6 +207,56 @@ Never silently continue with unverified credentials — the user must explicitly
 
 ---
 
+### Q2c (Jira and Linear only): Git host token
+
+When the board is **Jira** or **Linear**, Clancy needs a git host token to create pull requests after implementation. Skip this step entirely for **GitHub Issues** — the `GITHUB_TOKEN` collected in Q2 already covers PR creation.
+
+Output:
+
+```
+Clancy can push your feature branch and create a pull request automatically.
+Which git host does this project use?
+
+[1] GitHub
+[2] GitLab
+[3] Bitbucket
+[4] Skip — I'll push and create PRs manually
+```
+
+**If [1] GitHub:**
+
+`Paste your GitHub personal access token: (needs repo scope — create at github.com/settings/tokens)`
+
+Store as `GITHUB_TOKEN` in `.clancy/.env`.
+
+Verify by calling `GET https://api.github.com/user` with `Authorization: Bearer {token}` and `X-GitHub-Api-Version: 2022-11-28`.
+
+On success: `✅ GitHub connected — {login}`
+On failure: offer re-enter or skip (same pattern as Q2b).
+
+**If [2] GitLab:**
+
+`Paste your GitLab personal access token: (needs api scope — create at gitlab.com/-/user_settings/personal_access_tokens)`
+
+Store as `GITLAB_TOKEN` in `.clancy/.env`.
+
+If the user is using a self-hosted GitLab instance, also ask:
+`What's your GitLab API base URL? (e.g. https://gitlab.example.com/api/v4 — press Enter for gitlab.com)`
+
+If a URL is entered, store as `CLANCY_GIT_API_URL` in `.clancy/.env` and `CLANCY_GIT_PLATFORM="gitlab"`.
+If the user enters just a hostname or instance URL without `/api/v4`, append `/api/v4` automatically.
+
+**If [3] Bitbucket:**
+
+1. `What's your Bitbucket username? (your Atlassian account username)`
+2. `Paste your Bitbucket app password: (needs repository:write scope — create at bitbucket.org/account/settings/app-passwords)`
+
+Store as `BITBUCKET_USER` and `BITBUCKET_TOKEN` in `.clancy/.env`.
+
+**If [4] Skip:** no git host token is written. Clancy will still implement tickets but leave the feature branch for the user to push and create PRs manually.
+
+---
+
 ### Q3 (Jira only): Status name
 
 Output:
@@ -315,6 +365,47 @@ You can always configure these later via `/clancy:settings`.
 
 ---
 
+### Q3d-2 (Jira and Linear only): Review status
+
+Only ask this if a git host token was configured in Q2c (i.e. the user didn't skip PR creation).
+
+**GitHub:** Skip entirely — not applicable (GitHub Issues don't have workflow states).
+
+**Jira:** Output:
+
+```
+When Clancy creates a pull request, it can transition the ticket to a review status.
+
+What transition should Clancy use after creating a PR?
+
+[1] In Review
+[2] Ready for Review
+[3] Enter a different value
+[4] Skip — use the same status as completion (CLANCY_STATUS_DONE)
+```
+
+If [1]: store `CLANCY_STATUS_REVIEW="In Review"` in `.clancy/.env`.
+If [2]: store `CLANCY_STATUS_REVIEW="Ready for Review"` in `.clancy/.env`.
+If [3]: prompt for the value, store as `CLANCY_STATUS_REVIEW` in `.clancy/.env`. Wrap in double quotes.
+If [4] or the user says "skip"/"none": skip — no `CLANCY_STATUS_REVIEW` line written (falls back to `CLANCY_STATUS_DONE`).
+
+**Linear:** Output:
+
+```
+When Clancy creates a pull request, it can move the issue to a review state.
+
+What state should Clancy move an issue to after creating a PR?
+
+[1] In Review
+[2] Ready for Review
+[3] Enter a different value
+[4] Skip — use the same state as completion (CLANCY_STATUS_DONE)
+```
+
+Same storage logic as Jira above.
+
+---
+
 ### Q4: Base branch (auto-detect)
 
 Silently detect the base branch — do not ask unless detection fails:

package/src/roles/setup/workflows/scaffold.md

@@ -383,6 +383,18 @@ MAX_ITERATIONS=5
 # "Done" can be any transition to a post-implementation status.
 # CLANCY_STATUS_IN_PROGRESS="In Progress"
 # CLANCY_STATUS_DONE="Done"
+# CLANCY_STATUS_REVIEW="In Review"        # used when creating a PR instead of merging locally
+
+# ─── Optional: Git host (PR creation) ───────────────────────────────────────
+# When a ticket has no parent epic, Clancy pushes the feature branch and creates
+# a pull request instead of squash-merging locally. Requires a git host token.
+# GitHub Issues users already have GITHUB_TOKEN above — no extra config needed.
+# GITHUB_TOKEN=ghp_your-token              # if your git host is GitHub
+# GITLAB_TOKEN=glpat-your-token            # if your git host is GitLab
+# BITBUCKET_USER=your-username             # if your git host is Bitbucket
+# BITBUCKET_TOKEN=your-app-password        # if your git host is Bitbucket
+# CLANCY_GIT_PLATFORM=gitlab               # override auto-detection (github/gitlab/bitbucket)
+# CLANCY_GIT_API_URL=https://gitlab.example.com/api/v4  # self-hosted git API base URL
 
 # ─── Optional: Planner queue ─────────────────────────────────────────────────
 # Status for backlog tickets that /clancy:plan fetches from (default: Backlog)
@@ -419,6 +431,10 @@ GITHUB_REPO=owner/repo-name
 # When an issue has a milestone, Clancy auto-creates milestone/{slug} from this branch.
 CLANCY_BASE_BRANCH=main
 
+# ─── PR creation ─────────────────────────────────────────────────────────────
+# When an issue has no milestone, Clancy pushes the feature branch and creates a
+# PR using your GITHUB_TOKEN above. No extra config needed for GitHub Issues users.
+
 # ─── Loop ─────────────────────────────────────────────────────────────────────
 # Max tickets to process per /clancy:run session (default: 20)
 MAX_ITERATIONS=20
@@ -495,6 +511,17 @@ MAX_ITERATIONS=20
 # "Done" can be any post-implementation state (e.g. "Ready for Review", "In Review").
 # CLANCY_STATUS_IN_PROGRESS="In Progress"
 # CLANCY_STATUS_DONE="Done"
+# CLANCY_STATUS_REVIEW="In Review"        # used when creating a PR instead of merging locally
+
+# ─── Optional: Git host (PR creation) ───────────────────────────────────────
+# When an issue has no parent, Clancy pushes the feature branch and creates a
+# pull request instead of squash-merging locally. Requires a git host token.
+# GITHUB_TOKEN=ghp_your-token              # if your git host is GitHub
+# GITLAB_TOKEN=glpat-your-token            # if your git host is GitLab
+# BITBUCKET_USER=your-username             # if your git host is Bitbucket
+# BITBUCKET_TOKEN=your-app-password        # if your git host is Bitbucket
+# CLANCY_GIT_PLATFORM=gitlab               # override auto-detection (github/gitlab/bitbucket)
+# CLANCY_GIT_API_URL=https://gitlab.example.com/api/v4  # self-hosted git API base URL
 
 # ─── Optional: Notifications ──────────────────────────────────────────────────
 # Webhook URL for Slack or Teams notifications on ticket completion

package/src/roles/setup/workflows/settings.md

@@ -59,6 +59,7 @@ Jira
   [B3] Label filter      {CLANCY_LABEL if set, else off}
   [B4] Pickup status     {CLANCY_STATUS_IN_PROGRESS if set, else off}
   [B5] Done status       {CLANCY_STATUS_DONE if set, else off}
+  [B6] Review status     {CLANCY_STATUS_REVIEW if set, else "uses Done status"}
 
 {If GitHub:}
 GitHub
@@ -69,6 +70,7 @@ Linear
   [B1] Label filter      {CLANCY_LABEL if set, else off}
   [B2] Pickup status     {CLANCY_STATUS_IN_PROGRESS if set, else off}
   [B3] Done status       {CLANCY_STATUS_DONE if set, else off}
+  [B4] Review status     {CLANCY_STATUS_REVIEW if set, else "uses Done status"}
 
 Roles
   [R1] Planner           {✅ enabled / ─ disabled}
@@ -82,6 +84,9 @@ Planner
 {If Linear:}
   [P1] Plan state type    {CLANCY_PLAN_STATE_TYPE:-backlog}
 
+Git Host (PR creation)
+  [H1] Git host token    {platform: GitHub/GitLab/Bitbucket or "not set"}
+
 Integrations
   [I1] Figma MCP         {enabled if FIGMA_API_KEY set, else not set}
   [I2] Playwright        {enabled if PLAYWRIGHT_ENABLED=true, else off}
@@ -232,6 +237,23 @@ If [2]: remove `CLANCY_STATUS_DONE` from `.clancy/.env`.
 
 ---
 
+### [B6] Jira Review status (Jira only)
+
+```
+Jira Review status — current: {value or "uses Done status"}
+When Clancy creates a pull request (instead of merging locally), it transitions
+the ticket to this status. Falls back to CLANCY_STATUS_DONE if not set.
+
+[1] Set status name
+[2] Off (use Done status for PR flow too)
+[3] Cancel
+```
+
+If [1]: prompt `What status name should Clancy use for In Review? (e.g. In Review, Ready for Review, Code Review)` then write `CLANCY_STATUS_REVIEW=<value>` to `.clancy/.env`.
+If [2]: remove `CLANCY_STATUS_REVIEW` from `.clancy/.env`.
+
+---
+
 ### [B1] Linear label filter (Linear only)
 
 ```
@@ -283,6 +305,23 @@ If [2]: remove `CLANCY_STATUS_DONE` from `.clancy/.env`.
 
 ---
 
+### [B4] Linear Review status (Linear only)
+
+```
+Linear Review status — current: {value or "uses Done state"}
+When Clancy creates a pull request (instead of merging locally), it moves
+the issue to this state. Falls back to CLANCY_STATUS_DONE if not set.
+
+[1] Set state name
+[2] Off (use Done state for PR flow too)
+[3] Cancel
+```
+
+If [1]: prompt `What workflow state name should Clancy use for In Review? (e.g. In Review, Ready for Review, Code Review)` then write `CLANCY_STATUS_REVIEW=<value>` to `.clancy/.env`.
+If [2]: remove `CLANCY_STATUS_REVIEW` from `.clancy/.env`.
+
+---
+
 ### [R1] Planner role
 
 ```
@@ -355,6 +394,28 @@ If [3]: prompt `What state type should /clancy:plan fetch from?` then write `CLA
 
 ---
 
+### [H1] Git host token
+
+Only shown for Jira and Linear boards. GitHub Issues users already have `GITHUB_TOKEN` for PR creation.
+
+```
+Git host — current: {GitHub / GitLab / Bitbucket / not set}
+Clancy pushes feature branches and creates PRs on your git host.
+
+[1] GitHub
+[2] GitLab
+[3] Bitbucket
+[4] Remove (push and create PRs manually)
+[5] Cancel
+```
+
+If [1]: prompt `Paste your GitHub personal access token:` then write `GITHUB_TOKEN=<value>` to `.clancy/.env`. Remove any existing `GITLAB_TOKEN`, `BITBUCKET_USER`, `BITBUCKET_TOKEN`.
+If [2]: prompt `Paste your GitLab personal access token:` then write `GITLAB_TOKEN=<value>` to `.clancy/.env`. Optionally ask for a self-hosted API base URL (e.g. `https://gitlab.example.com/api/v4`) and write `CLANCY_GIT_API_URL` and `CLANCY_GIT_PLATFORM="gitlab"`. If the user enters just a hostname or instance URL without `/api/v4`, append `/api/v4` automatically. Remove any existing `GITHUB_TOKEN` (only if board is not GitHub), `BITBUCKET_USER`, `BITBUCKET_TOKEN`.
+If [3]: prompt for `Bitbucket username` and `Bitbucket app password`, write `BITBUCKET_USER` and `BITBUCKET_TOKEN` to `.clancy/.env`. Remove any existing `GITHUB_TOKEN` (only if board is not GitHub), `GITLAB_TOKEN`.
+If [4]: remove all git host token vars (`GITLAB_TOKEN`, `BITBUCKET_USER`, `BITBUCKET_TOKEN`, `CLANCY_GIT_PLATFORM`, `CLANCY_GIT_API_URL`). Keep `GITHUB_TOKEN` only if board is GitHub Issues.
+
+---
+
 ### [I1] Figma MCP
 
 ```
@@ -479,6 +540,7 @@ If no: print `Cancelled. No changes made.` and loop back to the menu.
    - Jira: `JIRA_BASE_URL`, `JIRA_USER`, `JIRA_API_TOKEN`, `JIRA_PROJECT_KEY`, `CLANCY_JQL_STATUS`, `CLANCY_JQL_SPRINT`
    - GitHub: `GITHUB_TOKEN`, `GITHUB_REPO`
    - Linear: `LINEAR_API_KEY`, `LINEAR_TEAM_ID`
+   - Git host (all boards): `GITLAB_TOKEN`, `BITBUCKET_USER`, `BITBUCKET_TOKEN`, `CLANCY_GIT_PLATFORM`, `CLANCY_GIT_API_URL`, `CLANCY_STATUS_REVIEW`
 2. Write the new board credentials to `.clancy/.env`
 3. If switching to Jira: also ask the status filter question (same as init Q3) and write `CLANCY_JQL_STATUS` to `.clancy/.env`
 4. No script replacement needed — the bundled runtime scripts are board-agnostic (board detection happens at runtime from `.clancy/.env`)