report-out

Generates Dutch Slack reports from git and GitHub activity scans.

1|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ConductionNL/shillinq --skill report-out
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: report-out
Source: https://github.com/ConductionNL/shillinq/tree/main/.claude/skills/report-out
Command: npx skills add https://github.com/ConductionNL/shillinq --skill report-out

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, git, jq, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill eliminates the manual overhead of tracking daily git activity, managing PRs, and drafting status updates, ensuring your work is always documented and your team is kept in the loop.

Core Features & Use Cases

  • Automated Reporting: Scans local repositories and GitHub activity to generate a ready-to-paste Dutch Slack report.
  • Workflow Management: Suggests PR creation for orphan branches and manages issue lifecycles with intelligent status tracking.
  • Use Case: At the end of a busy day, use this Skill to quickly summarize your commits, update your tracking issues, and generate a professional report-out message without leaving your terminal.

Quick Start

Invoke the report-out skill to scan your local repositories and generate your end-of-day Slack report.

Frequently Asked Questions about report-out

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

FAQPage Schema
How do I automate daily git activity tracking and status reporting?

Automate daily git activity tracking by scanning local repositories and GitHub interactions to generate end-of-day status reports. This skill dynamically resolves your user identity and repository scope to summarize commits and update tracking issues.

How does automated pull request management work for orphan branches?

Automated pull request management works by scanning local repositories for orphan branches and suggesting PR creation. It also manages issue lifecycles using intelligent status tracking based on your local git configuration and GitHub activity.

Do I need the GitHub CLI to generate end-of-day Slack reports from git?

Yes, you need the GitHub CLI and local git configuration to generate end-of-day Slack reports. The skill requires these dependencies to dynamically resolve user identity, scan repository scope, and interact with GitHub pull requests and issues.

Can I use this workflow automation for managing GitHub issue lifecycles?

Yes, you can use this workflow automation for managing GitHub issue lifecycles. It scans your GitHub interactions to suggest issue updates and tracks their statuses intelligently alongside your daily commit activity.

What is the best way to summarize my commits into a Slack report?

The best way to summarize commits into a Slack report is scanning local repositories and GitHub activity to generate a ready-to-paste message. This workflow automation produces a professional Dutch Slack report without leaving your terminal.

What are the limitations of using local git configuration for workflow reporting?

A limitation of using local git configuration for workflow reporting is the strict dependency on local setup. You must have the GitHub CLI, git, and jq installed, and your local repositories must be properly configured to resolve user identity and repository scope.