- Home
- Skills
- Charlesjones Dev
- Claude Code Plugins Dev
- Ado Timesheet Report
ado-timesheet-report_skill
26
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill charlesjones-dev/claude-code-plugins-dev --skill ado-timesheet-report- SKILL.md40.9 KB
Overview
This skill generates a summarized weekly timesheet report of hours logged on Azure DevOps work items. It produces a hierarchical tree (Feature > User Story > Task) or date-grouped view and supports flexible filters for closed, worked-on, or both task types. The report rolls up "Completed Work" hours and supports three verbosity levels for output detail.
How this skill works
The skill first validates Azure DevOps configuration in the project CLAUDE.md and extracts organization and project values. It then interactively collects reporting parameters (week definition, time period, task filters, date field, verbosity, grouping, and user) and calculates the exact ISO date range. Finally it retrieves work items for the authenticated user, applies client-side filtering, aggregates Completed Work hours, and formats results by hierarchy or date.
When to use it
- When you need a weekly summary of hours rolled up by Feature > User Story > Task.
- When auditing time logged for closed, worked-on, or both types of tasks during a specific week.
- When you want date-grouped or hierarchy-grouped views for payroll or status reporting.
- When you need configurable verbosity to include IDs, titles, descriptions, and hours.
- When you want to report on the current user or a specific team member.
Best practices
- Ensure CLAUDE.md contains an "## Azure DevOps" section before running the report.
- Choose Changed Date for filters when reporting on work that was updated but not closed.
- Use the Specific week option only when you can supply a valid week-ending date in YYYY-MM-DD format.
- Select grouping and verbosity appropriate to your audience—use Level 1 for quick audits and Level 3 for detailed reviews.
- Run /ado-init to configure Azure DevOps if configuration is missing; the skill will not proceed without it.
Example use cases
- Generate last week’s timesheet for a sprint retrospective grouped by Feature and User Story.
- Produce a current-week report of worked-on tasks for a developer to verify billed hours.
- Create a date-grouped report for payroll to reconcile daily logged hours across tasks.
- Run a detailed Level 3 report for a manager reviewing task descriptions and hours.
- Check closed-only tasks for compliance reporting over a specified week.
FAQ
The skill stops and instructs you to run the project initialization command to configure Azure DevOps; it will not proceed without the configuration.
Can I pass the week or dates as command arguments?
No. This command ignores any inline arguments and collects all parameters interactively using the built-in question flow.