Menu
Build weekly status reports from git history and issue tracker exports
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Create a Pull Request for the current branch
Review an open PR before approving it
Analyze upstream specs (agentskills.io, Claude Code plugin/marketplace format, OpenClaw, MCP, CodeRabbit, APM) for changes, identify gaps in skillsaw's rule coverage, and create or update PRs to close those gaps. Use when performing periodic maintenance on the skillsaw linter.
Create a skillsaw rule plugin — a pip-installable Python package that adds custom lint rules to skillsaw. Walks through scaffolding the package, writing rules against the lint tree, testing, and publishing to PyPI. Use when a user wants to share skillsaw rules across repositories or publish them for others.
Survey the AI coding assistant and agentic tool ecosystem, assess skillsaw's competitive position, identify emerging patterns and missing capabilities, and produce a prioritized strategic report as a GitHub issue.
Fix skillsaw lint violations — apply deterministic autofixes, then resolve the remaining violations with targeted edits guided by `skillsaw explain`. Use when skillsaw reports violations, when asked to clean up lint findings, or after `skillsaw fix` leaves violations behind.
| name | report-builder |
| description | Build weekly status reports from git history and issue tracker exports |
| compatibility | Requires Python 3.9+ and git |
| metadata | {"author":"dx-team","version":"1.0"} |
Build a weekly status report from git history and an issue tracker export.
Use when the user asks for a weekly status report, a sprint summary, or a change digest for a repository.
Run the bundled builder to collect commits and issue updates:
python scripts/build.py --since "1 week ago" --output report.html
Follow the formatting rules in the style guide
when editing the generated sections. HTML templates for the report
shell live in the assets/ directory.
Attach the generated report.html and paste the summary section into
the status channel.