Run any Skill in Manus with one click

sfa-jira-standup

Stars0

Forks9

UpdatedMarch 25, 2026 at 10:08

Generate a daily standup report from Jira for a Server Foundation team member. Use this skill when the user wants a standup summary, daily update, or asks 'what did I do yesterday', 'standup', 'daily update', 'my status'. Queries Jira to find recently updated and in-progress issues, then formats a standup report.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

stolostron

stolostron/server-foundation-agent

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	sfa-jira-standup
description	Generate a daily standup report from Jira for a Server Foundation team member. Use this skill when the user wants a standup summary, daily update, or asks 'what did I do yesterday', 'standup', 'daily update', 'my status'. Queries Jira to find recently updated and in-progress issues, then formats a standup report.

Jira Standup Report

Generate a daily standup report from Jira issues.

Reference Loading

For JQL syntax: Read docs/jira/jql-reference.md
For API details: Read docs/jira/api-reference.md

Parameters

Parameter	Required	Default	Notes
assignee	No	current user	Team member name/email
days	No	1	How many days back to look for "Done" items

Workflow

Step 1: Resolve assignee

If specified, look up in team-members/team-members.md. Otherwise use currentUser().

Step 2: Run two JQL queries

Query 1 — What I did (updated yesterday/recently):

project = ACM AND component = "Server Foundation" AND assignee = <user> AND updated >= -<days>d AND status IN (Resolved, Closed, Review, Testing)

Query 2 — What I'm doing (in progress):

project = ACM AND component = "Server Foundation" AND assignee = <user> AND status IN ("In Progress", "New")

Use /rest/api/3/search/jql POST for both. Request fields: ["issuetype", "summary", "status", "priority", "updated"].

Step 3: Format standup report

## Standup Report — <Name> (<date>)

### Done (updated in last <N> day(s))
- [ACM-12345](https://redhat.atlassian.net/browse/ACM-12345) Fix proxy cert rotation — *Resolved*
- [ACM-12346](https://redhat.atlassian.net/browse/ACM-12346) Update go dependencies — *Review*

### In Progress
- [ACM-12347](https://redhat.atlassian.net/browse/ACM-12347) Implement addon health check — *In Progress*
- [ACM-12348](https://redhat.atlassian.net/browse/ACM-12348) Investigate flaky test — *New*

### Blockers
<None identified — ask the user if they have any>

Step 4: Ask about blockers

After presenting the report, ask: "Any blockers to add?"

Examples

/sfa-jira-standup
What did I do yesterday?
Standup for zhiwei

More from this repository

same repository

sfa-cve-analysis

stolostron/server-foundation-agent

Monitor and analyze CVE (security) issues for Server Foundation team. Groups by CVE, creates one tracking task per CVE (consolidates all affected repositories), and performs deep impact analysis across all branches.

2026-06-190

sfa-github-fetch-prs

stolostron/server-foundation-agent

Fetch/Get/View all active(open) pull requests of sf(server foundation) team. For example: `How many sf PRs opened today?` sometimes user may omit `sf`, directly say `How many PRs opened today?`, if user's context does not contain any other PR related information, then it is assumed that the user intends to query the PRs of the sf team.

2026-06-170

sfa-bug-analyze

stolostron/server-foundation-agent

Analyze a Jira bug for Server Foundation relevance and reproducibility. Use this skill when the user wants to check if a bug can be reproduced, assess if it has enough information, or verify SF team ownership. Trigger phrases: 'analyze bug', 'check bug reproducibility', 'can we reproduce ACM-12345', 'is this bug reproducible', 'analyze ACM-12345', 'check if bug is SF-related'.

2026-05-290

sfa-bug-reproduce

stolostron/server-foundation-agent

Orchestrate full bug reproduction workflow: analyze bug, provision ACM cluster, execute test, capture results, and post to Jira. Use this skill when the user wants to reproduce a bug end-to-end, set up a test environment for a bug, or says 'reproduce bug ACM-12345', 'test ACM-12345', 'reproduce this bug automatically'.

2026-05-290

sfa-repo-architecture

stolostron/server-foundation-agent

Generate an architectural overview of upstream OCM-io vs downstream stolostron repos for Server Foundation. Clones all repos, analyzes their code, and produces a Mermaid-diagrammed markdown file at the repo root. Trigger phrases: 'generate architecture doc', 'repo architecture', 'upstream downstream diagram', 'ocm vs stolostron', 'generate repo overview'.

2026-05-270

sfa-jira-triage

stolostron/server-foundation-agent

Generate a bug triage report for the Server Foundation team. Use this skill when the user wants to triage bugs, review new issues, check for unassigned bugs, or says 'triage bugs', 'new bugs', 'bug review', 'unassigned bugs', 'vulnerability review'. Queries Jira for recently created or unresolved bugs and formats a triage summary.

2026-04-080

name	sfa-jira-standup
description	Generate a daily standup report from Jira for a Server Foundation team member. Use this skill when the user wants a standup summary, daily update, or asks 'what did I do yesterday', 'standup', 'daily update', 'my status'. Queries Jira to find recently updated and in-progress issues, then formats a standup report.

Jira Standup Report

Generate a daily standup report from Jira issues.

Reference Loading

For JQL syntax: Read docs/jira/jql-reference.md
For API details: Read docs/jira/api-reference.md

Parameters

Parameter	Required	Default	Notes
assignee	No	current user	Team member name/email
days	No	1	How many days back to look for "Done" items

Workflow

Step 1: Resolve assignee

If specified, look up in team-members/team-members.md. Otherwise use currentUser().

Step 2: Run two JQL queries

Query 1 — What I did (updated yesterday/recently):

project = ACM AND component = "Server Foundation" AND assignee = <user> AND updated >= -<days>d AND status IN (Resolved, Closed, Review, Testing)

Query 2 — What I'm doing (in progress):

project = ACM AND component = "Server Foundation" AND assignee = <user> AND status IN ("In Progress", "New")

Use /rest/api/3/search/jql POST for both. Request fields: ["issuetype", "summary", "status", "priority", "updated"].

Step 3: Format standup report

## Standup Report — <Name> (<date>)

### Done (updated in last <N> day(s))
- [ACM-12345](https://redhat.atlassian.net/browse/ACM-12345) Fix proxy cert rotation — *Resolved*
- [ACM-12346](https://redhat.atlassian.net/browse/ACM-12346) Update go dependencies — *Review*

### In Progress
- [ACM-12347](https://redhat.atlassian.net/browse/ACM-12347) Implement addon health check — *In Progress*
- [ACM-12348](https://redhat.atlassian.net/browse/ACM-12348) Investigate flaky test — *New*

### Blockers
<None identified — ask the user if they have any>

Step 4: Ask about blockers

After presenting the report, ask: "Any blockers to add?"

Examples

/sfa-jira-standup
What did I do yesterday?
Standup for zhiwei