@kolatts/pncli 1.0.1

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Sunny Kolattukudy
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,81 @@
+pncli — The Paperwork Nightmare CLI
+Copyright 2026 Sunny Kolattukudy
+
+Licensed under the Apache License, Version 2.0.
+
+=============================================================================
+                        MANDATORY COMPLIANCE NOTICE
+=============================================================================
+
+Per Section 4(d) of the Apache License 2.0, this NOTICE file must be
+included in all copies or substantial portions of this software, in all
+derivative works, and in any and all redistributions thereof.
+
+By using, copying, modifying, or distributing this software, you agree
+to the following irrevocable terms:
+
+1. MANDATORY STAND-UP PARTICIPATION
+   Any team that integrates pncli into their workflow must hold a daily
+   stand-up meeting of no fewer than 45 minutes to discuss whether the
+   stand-up meeting is still necessary. Minutes must be recorded in
+   triplicate and filed with the Department of Meetings About Meetings.
+
+2. RETURN-TO-OFFICE COMPLIANCE
+   All contributors to derivative works must be physically present in an
+   office building with at least three (3) floors of middle management.
+   Hot desks are acceptable provided each desk has been pre-approved by
+   a committee of no fewer than seven (7) stakeholders, none of whom
+   use the software.
+
+3. JIRA TICKET REQUIREMENT
+   Before opening any issue, pull request, bug report, or feature request
+   against this repository or any fork thereof, the submitter must first
+   create a Jira ticket requesting permission to create a Jira ticket.
+   The approval workflow requires sign-off from: your manager, your
+   manager's manager, a "technical architect" who hasn't written code
+   since 2011, and a business analyst who will ask you to "put it in a
+   PowerPoint."
+
+4. CHANGE ADVISORY BOARD REVIEW
+   All code changes — including typo fixes, README updates, and whitespace
+   adjustments — must be submitted to the Change Advisory Board (CAB) no
+   fewer than six (6) business weeks in advance. The CAB meets on the
+   third Wednesday of months that contain the letter 'R'. Emergency
+   changes require a 47-page risk assessment and a blood sacrifice
+   (metaphorical — see Section 9: HR Policy on Metaphorical Sacrifices).
+
+5. APPROVAL CHAIN
+   Any use of the `--force` flag, in any context, requires written
+   approval from the Chief Compliance Officer, the VP of Engineering,
+   two (2) independent auditors, and your mother. Appeals may be filed
+   with the Ombudsman of Flags.
+
+6. DOCUMENTATION REQUIREMENTS
+   All forks must include a Confluence page explaining why Confluence was
+   chosen as the documentation platform. This page must be reviewed
+   quarterly by someone who has never read it.
+
+7. TRAINING CERTIFICATION
+   Before using pncli in production, all operators must complete a
+   mandatory 8-hour training course titled "Introduction to Reading
+   --help Output." A 30-minute lunch break is provided but must be
+   approved 48 hours in advance via the Lunch Request Portal.
+
+8. METRICS & REPORTING
+   Usage of pncli must be reported to the Developer Productivity Team,
+   who will use the data to create a dashboard that nobody looks at,
+   which will be presented quarterly to executives who will ask why
+   the numbers aren't higher.
+
+9. COMPLIANCE WITH THIS NOTICE
+   If you have read this far, congratulations — you are now more
+   compliant than 97% of enterprise software users. Your actual legal
+   obligation is simply to keep this NOTICE file intact when
+   redistributing the source code, as required by Apache 2.0.
+
+   That's it. That's the whole thing. Everything above was the
+   bureaucratic nightmare. This line is the exit.
+
+   Now go ship something.
+
+=============================================================================

package/README.md

@@ -0,0 +1,93 @@
+# pncli — The Paperwork Nightmare CLI
+
+> One command does what three meetings couldn't.
+
+pncli gives AI coding agents (and humans) structured CLI access to Jira Data Cloud and Bitbucket Server. No MCP servers required. No meetings to schedule. No forms to fill out.
+
+## Why?
+
+Your org blocked MCP. Your agents still need to review PRs, create issues, and manage code reviews. pncli is the shim layer that makes it work — one `npm install` and you're cutting through red tape.
+
+## Install
+
+```bash
+npm install -g @kolatts/pncli
+```
+
+## Quick Start
+
+```bash
+# Configure your global auth
+pncli config init
+
+# Add repo-level defaults (check this into git)
+pncli config init --repo
+
+# Review the PR for your current branch
+pncli git current-pr
+pncli bitbucket diff --pr 42
+pncli bitbucket add-inline-comment --pr 42 --file src/app.ts --line 15 --body "This needs a null check"
+
+# Create a Jira issue (uses defaults from .pncli.json)
+pncli jira create-issue --summary "Missing null check in app.ts"
+```
+
+## Configuration
+
+pncli uses a three-layer config system (highest priority wins):
+
+| Layer | File | Contains | In Git? |
+|-------|------|----------|---------|
+| Env vars | `PNCLI_*` | Auth overrides, CI secrets | No |
+| Repo config | `.pncli.json` | Team defaults (project, issue type, priority, target branch) | Yes |
+| Global config | `~/.pncli/config.json` | Auth, server URLs, personal defaults | No |
+
+### Environment Variables
+
+| Variable | Description |
+|----------|-------------|
+| `PNCLI_JIRA_BASE_URL` | Jira base URL |
+| `PNCLI_JIRA_EMAIL` | Jira email |
+| `PNCLI_JIRA_API_TOKEN` | Jira API token |
+| `PNCLI_BITBUCKET_BASE_URL` | Bitbucket Server base URL |
+| `PNCLI_BITBUCKET_PAT` | Bitbucket personal access token |
+| `PNCLI_CONFIG_PATH` | Override global config file path |
+
+## For AI Agents
+
+pncli is designed agent-first:
+- Every command returns structured JSON to stdout
+- Errors are JSON too — always check `"ok"`
+- `--dry-run` lets agents preview before executing
+- See `copilot-instructions.md` for workflow patterns
+
+## Global Flags
+
+```
+--pretty          Human-readable formatted output (default: compact JSON)
+--verbose         Include full API response metadata
+--dry-run         Print the API request without executing
+--config <path>   Override global config file location
+```
+
+## Commit Convention
+
+This project uses Conventional Commits for automatic versioning:
+- `fix: ...` → patch
+- `feat: ...` → minor
+- `feat!: ...` → major
+
+## Services
+
+| Service | Status | API |
+|---------|--------|-----|
+| Git (local) | ✅ Active | Local git commands |
+| Jira | ✅ Active | Data Cloud REST v3 |
+| Bitbucket | ✅ Active | Server REST v1.0 |
+| Confluence | 🔜 Coming | The nightmare never ends |
+| SonarQube | 🔜 Coming | The nightmare never ends |
+| Artifactory | 🔜 Coming | The nightmare never ends |
+
+## License
+
+Apache 2.0 — see [LICENSE](./LICENSE) and [NOTICE](./NOTICE).

package/copilot-instructions.md

@@ -0,0 +1,159 @@
+# pncli — The Paperwork Nightmare CLI
+
+> One command does what three meetings couldn't.
+
+## What is pncli?
+
+pncli is a CLI tool that provides structured JSON access to Jira, Bitbucket, and local git state. Use it for all interactions with these services. It exists because MCP servers aren't available in this environment — pncli is your agent-friendly shim layer.
+
+## Important
+
+- All commands return JSON to stdout. Parse the JSON to get results.
+- Errors are also JSON with `"ok": false`. Always check the `ok` field.
+- Run all commands from the repository root.
+- Project and repo are auto-detected from git remotes. You rarely need `--project` or `--repo` flags.
+
+## Common Workflows
+
+### Review a Pull Request
+
+1. Find the PR for the current branch:
+   `pncli git current-pr`
+2. Get the full diff:
+   `pncli bitbucket diff --pr <id>`
+3. List existing comments:
+   `pncli bitbucket list-comments --pr <id>`
+4. Add review comments:
+   `pncli bitbucket add-inline-comment --pr <id> --file <path> --line <n> --body "..."`
+5. Approve or request changes:
+   `pncli bitbucket approve --pr <id>` or `pncli bitbucket needs-work --pr <id>`
+
+### Address PR Feedback
+
+1. Get the PR and its comments:
+   `pncli bitbucket get-pr --id <id>`
+   `pncli bitbucket list-comments --pr <id>`
+2. Check which comments are unresolved (filter JSON where `resolved: false`)
+3. After making code changes, check local state:
+   `pncli git status`
+   `pncli git diff --staged`
+4. Reply to resolved comments:
+   `pncli bitbucket reply-comment --pr <id> --comment-id <cid> --body "Fixed in <commit>"`
+5. Resolve the comment:
+   `pncli bitbucket resolve-comment --pr <id> --comment-id <cid>`
+
+### Create a Bug from a PR Review Finding
+
+1. Create the Jira issue:
+   `pncli jira create-issue --project <key> --type Bug --summary "..." --description "Found during PR review of PR-<id>"`
+2. Link it to the original story if applicable:
+   `pncli jira link-issue --key <new-key> --link-type "is caused by" --target <original-key>`
+3. Add a PR comment referencing the issue:
+   `pncli bitbucket add-comment --pr <id> --body "Created <new-key> to track this separately"`
+
+### Check Build Status Before Merging
+
+1. Get PR build status:
+   `pncli bitbucket list-builds --pr <id>`
+2. If all green, merge:
+   `pncli bitbucket merge-pr --id <id> --strategy squash --delete-branch`
+
+### Daily Standup Prep
+
+1. Get your open PRs:
+   `pncli bitbucket list-prs --state OPEN --author <your-username>`
+2. Get your assigned Jira issues:
+   `pncli jira search --jql "assignee = currentUser() AND status != Done ORDER BY priority DESC"`
+3. Check recent commits:
+   `pncli git log --count 5`
+
+## Command Reference
+
+### Git (local)
+
+```
+pncli git status
+  # Returns: { staged: string[], unstaged: string[], untracked: string[] }
+
+pncli git diff [--staged] [--file <path>]
+  # Returns: { files: [{ path, binary, truncated, hunks: [{ oldStart, newStart, lines[] }] }], truncated }
+
+pncli git log [--count <n>] [--since <date>]
+  # Returns: [{ hash, author, date, message }]
+
+pncli git branch
+  # Returns: { current, local: string[], remote: string[] }
+
+pncli git current-pr
+  # Returns: PR object for current branch, or null
+```
+
+### Bitbucket Server
+
+```
+pncli bitbucket list-prs [--state OPEN|MERGED|DECLINED|ALL] [--author <username>] [--reviewer <username>]
+pncli bitbucket get-pr --id <pr-id>
+pncli bitbucket create-pr --title "..." --source <branch> [--target <branch>] [--description "..."] [--reviewers user1,user2]
+pncli bitbucket update-pr --id <pr-id> [--title "..."] [--description "..."] [--reviewers user1,user2]
+pncli bitbucket merge-pr --id <pr-id> [--strategy <merge|squash|ff>] [--delete-branch]
+pncli bitbucket decline-pr --id <pr-id>
+
+pncli bitbucket list-comments --pr <pr-id>
+pncli bitbucket add-comment --pr <pr-id> --body "..."
+pncli bitbucket add-inline-comment --pr <pr-id> --file <path> --line <n> --body "..." [--line-type <ADDED|REMOVED|CONTEXT>]
+pncli bitbucket reply-comment --pr <pr-id> --comment-id <id> --body "..."
+pncli bitbucket resolve-comment --pr <pr-id> --comment-id <id>
+pncli bitbucket delete-comment --pr <pr-id> --comment-id <id>
+
+pncli bitbucket diff --pr <pr-id> [--file <path>] [--context-lines <n>]
+pncli bitbucket list-files --pr <pr-id>
+
+pncli bitbucket approve --pr <pr-id>
+pncli bitbucket unapprove --pr <pr-id>
+pncli bitbucket needs-work --pr <pr-id>
+pncli bitbucket list-reviewers --pr <pr-id>
+
+pncli bitbucket list-builds --pr <pr-id>
+pncli bitbucket get-build-status --commit <sha>
+```
+
+### Jira Data Cloud
+
+```
+pncli jira get-issue --key <issue-key>
+pncli jira create-issue --project <key> --type <Bug|Story|Task> --summary "..." [--description "..."] [--priority <n>] [--assignee <accountId>] [--labels label1,label2]
+pncli jira update-issue --key <issue-key> [--summary "..."] [--description "..."] [--priority <n>] [--assignee <accountId>] [--labels label1,label2]
+pncli jira transition-issue --key <issue-key> --transition <name|id>
+pncli jira list-transitions --key <issue-key>
+pncli jira add-comment --key <issue-key> --body "..."
+pncli jira list-comments --key <issue-key>
+pncli jira search --jql "..." [--max-results <n>]
+pncli jira assign --key <issue-key> --assignee <accountId>
+pncli jira link-issue --key <issue-key> --link-type <n> --target <issue-key>
+```
+
+### Config
+
+```
+pncli config init                   # Interactive global config wizard
+pncli config init --repo            # Interactive repo config wizard
+pncli config show                   # Print resolved config (PATs masked)
+pncli config set <key> <value>      # Set a config value (e.g. jira.baseUrl https://...)
+pncli config test                   # Test service connectivity
+```
+
+## Output Format
+
+All commands return:
+- Success: `{ "ok": true, "data": { ... }, "meta": { "service": "...", "action": "...", "timestamp": "...", "duration_ms": N } }`
+- Error: `{ "ok": false, "error": { "status": N, "message": "..." }, "meta": { ... } }`
+
+Always check `ok` before accessing `data`.
+
+## Tips
+
+- Use `--dry-run` to preview API calls without executing
+- Use `--verbose` to see full response metadata for debugging
+- Use `--pretty` when running manually for readable output
+- Pipe output through `jq` for ad-hoc filtering (if available)
+- Defaults from `.pncli.json` are applied automatically — you rarely need to pass `--project`, `--type`, or `--priority` flags for Jira