refined-prun
Official@refined-prun
Offers repository analysis, documentation restructuring, and pull request review management for engineering teams maintaining complex codebase standards.
Agent Skills by refined-prun
Showing 9 vetted skills indexed across 1 GitHub repositories.
bootstrap-docs
Analyze repository files to generate starter documentation and coverage manifests.
distill
Distill conversation reviews into corrections, facts, guidelines, and open questions.
resolve-review
Apply review resolutions from PR review files with per-finding commits.
create-skill
Create a slash-command skill with SKILL.md frontmatter and markdown phases.
restructure-docs
Restructure markdown documentation by splitting, merging, moving, or renaming files.
review-pr
Review GitHub pull requests against project guidelines and produce a structured review artifact.
save-plan
Save current analysis or plan into a dated markdown file under .tmp/plans.
explore-project
Analyze repository documentation, map directory structure, and regenerate an exploration manifest.
augment-review
Extract human review comments from a working copy into a pull request review file.
Frequently Asked Questions About refined-prun
FAQPage SchemaWhat specific tasks can I perform using refined-prun?▼
You can analyze repository file structures to generate documentation, review pull requests against project guidelines, distill conversation feedback into actionable corrections, and restructure markdown documentation files. It also supports saving analysis plans and creating new slash-command capabilities with structured frontmatter.
Which engineering personas benefit most from these capabilities?▼
Technical leads, documentation maintainers, and senior engineers managing large repositories benefit most. These capabilities assist those responsible for enforcing project guidelines, managing pull request review cycles, and maintaining high-quality, up-to-date documentation across complex codebases.
What are the prerequisites for implementing these repository management skills?▼
Implementation requires a local environment with access to the target repository and its associated pull request metadata. Users must ensure their project documentation follows standard markdown formatting to allow for effective parsing, restructuring, and manifest generation.