rls

Automate TrueNorth release tagging, status checks, diffs, and release notes via tnctl rls commands.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/popodidi/harvis --skill rls
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rls
Source: https://github.com/popodidi/harvis/tree/main/projects/truenorth/skills/rls
Command: npx skills add https://github.com/popodidi/harvis --skill rls

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Release management for TrueNorth involves coordinating tags, deployment status, diffs, and release notes across multiple services. This Skill automates those tasks to reduce manual effort and risk of miscommunication.

Core Features & Use Cases

  • Tag releases using tnctl rls tag to trigger deployments and create versioned artifacts for all relevant services.
  • Monitor deployment status across services with tnctl rls status, with optional filters by repo or service.
  • View diffs for a repository using tnctl rls diff to review pending changes before release.
  • Generate consolidated release notes across repos with tnctl rls note for stakeholder communication.

Quick Start

Use the rls skill to perform common release operations:

  • Check current status for a repo: tnctl rls status --repo=truenorth-web --output json
  • See pending changes for a repo: tnctl rls diff --repo=truenorth-web --output json
  • Dry-run a release tag: tnctl rls tag --repo=truenorth-web
  • Create and push a release tag (requires human approval): tnctl rls tag --repo=truenorth-web --minor --no-dryrun --push
  • Monitor deployment status: tnctl rls status --repo=truenorth-web --output json

Frequently Asked Questions about rls

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate release notes generation across multiple repositories?

You can automate release notes generation across multiple repositories by running the tnctl rls note command to consolidate pending changes across all TrueNorth components into unified release communication for stakeholders.

What's the best way to check multi-repo deployment status before a release?

The best way to check multi-repo deployment status before a release is by running tnctl rls status with optional repo or service filters, returning JSON outputs to monitor deployment progress across all TrueNorth components.

How does the human approval workflow work when tagging a release?

The human approval workflow for tagging a release requires explicit confirmation before executing tnctl rls tag with the --no-dryrun and --push flags, preventing accidental deployments while allowing dry-run tag operations first.

Can I review pending repository changes before triggering a deployment?

Yes, you can review pending repository changes before triggering a deployment by running tnctl rls diff for a specific repository, which outputs a JSON diff of pending changes to inspect before tagging or releasing.

Does tnctl support release management for individual services within a multi-repo deployment?

Yes, tnctl supports release management for individual services within multi-repo deployments through filtering options, allowing commands like tnctl rls status and tag to target specific repos or services rather than the entire stack.

Why do I need a dry-run when tagging releases for TrueNorth?

You need a dry-run when tagging releases for TrueNorth to safely preview versioned artifacts and deployment triggers without pushing tags, as running tnctl rls tag without the --no-dryrun flag validates the release configuration beforehand.