improve-rules

Promote recurring issues from logs into permanent rule files.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/hackberrybay/hb-code-reviewer --skill improve-rules-hackberrybay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: improve-rules
Source: https://github.com/hackberrybay/hb-code-reviewer/tree/main/skills/improve-rules
Command: npx skills add https://github.com/hackberrybay/hb-code-reviewer --skill improve-rules-hackberrybay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Promotes recurring issues logged during reviews into permanent rule entries to prevent repetitive work and ensure consistent improvements.

Core Features & Use Cases

  • Reads the recurring-issues log and identifies entries with 3+ occurrences that are not yet promoted.
  • Invokes the issue-logger agent in Promote mode to append new rules under the correct rule file (typescript.md or security.md) and marks promoted entries.
  • Generates a promotion report for sprint retrospectives and team visibility.

Quick Start

Run this skill after completing several review cycles to automatically elevate stable recurring issues into permanent rules.

Frequently Asked Questions about improve-rules

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

FAQPage Schema
How do I promote recurring issues into permanent rules after a sprint?

This skill promotes recurring issues into permanent rules by scanning your logs for problems appearing three or more times and appending them to rule files like typescript.md or security.md after a sprint.

What is the threshold for an issue to become a permanent rule entry?

An issue must appear three or more times in the recurring-issues log to qualify for promotion into a permanent rule file, ensuring only stable and repetitive problems are elevated.

How does rule management automation handle typescript and security issues?

Rule management automation handles these issues by invoking the issue-logger agent in Promote mode, which appends qualifying recurring issues to the appropriate typescript.md or security.md rule files.

When should I run the process to elevate recurring issues into rule files?

You should run this process after completing several review cycles or at the end of a sprint, ensuring enough log data has accumulated to identify stable recurring issues for permanent rule promotion.

Can I generate a promotion report for sprint retrospectives from recurring issues?

Yes, the skill generates a promotion report for sprint retrospectives after reading the recurring-issues log and updating rule files, providing team visibility into newly promoted permanent rules.