AGENTS.mdA
AGENTS.md from pchuri/jira-cli is an AGENTS.md file: the standing instructions coding agents read in that repo.
mdr add pchuri/jira-cli/AGENTS.md@git:20251210.97cb85cPins git:20251210.97cb85c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- AGENTS.md file
- Repository
- pchuri/jira-cli
- Path
AGENTS.md- Versions recorded
- 1
- Latest version
- git:20251210.97cb85c, committed Dec 10, 2025
- Size
- 2,137 bytes
- Repository stars
- 17
- License
- ISC
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Agents Release Playbook ## Purpose Capture fallback release steps for situations where a recent bug fix skipped automation because the commit missed the Conventional Commits format. ## ✅ Best Practice: Use Conventional Commits Always use proper Conventional Commit messages to let semantic-release work automatically: - `feat:` → MINOR version bump (e.g., 1.0.0 → 1.1.0) - `fix:` → PATCH version bump (e.g., 1.0.0 → 1.0.1) - `BREAKING CHANGE:` → MAJOR version bump (e.g., 1.0.0 → 2.0.0) **Recent success example**: PR #7 used `feat: support token-only authentication without username` and automatically released v1.1.0 ✨ --- ## Fallback Options (when automation fails) ### Option 1: Trigger semantic-release with an empty commit 1. Branch from the latest `main` or `beta`. 2. Confirm the fix is already on that branch and CI is green, then create the empty commit. ```bash git commit --allow-empty -m "fix: trigger release after hotfix" ``` 3. Open a PR; once checks pass, merge into `main` or `beta`. 4. The merge runs the Release workflow and bumps the patch version. ## Option 2: Manual version bump (last resort) …
Read the whole file at its exact version.
How to install
mdr add pchuri/jira-cli/AGENTS.md@sha256:2fd8490ffe2d007dThe line at the top of this page pins the label git:20251210.97cb85c, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_atrsrudmlyertuhv)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Dec 10, 2025.
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (2137 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
pchuri/jira-cli · 17 stars · license ISC · pushed 2026-10-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_atrsrudmlyertuhv GET https://markdownregistry.com/api/v1/resolve?ref=pchuri/jira-cli/AGENTS.md GET https://markdownregistry.com/api/v1/blob/2fd8490ffe2d007d9601214213a72becc2d7d51ba88bfb239c756dbc84646cc2
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: how to write a good AGENTS.md · AGENTS.md vs CLAUDE.md · which agent file does what.